RDS 2012 - unable to connect to SH via webgateway

Question

Dear all,
we have setup a RDS 2012 system following this article;
rds8-standard-3-node-remoteapp-deployment-on-windows-server-2012
It all went ok as far is I could see but Im running into the following problem.
If I use MSTSC to connect through the gateway directly things work, I get the desired SH desktop without a problem. (eg connect to SH001.domain.local using the web url for the gateway/webserver).
If I go to the external website and try to setup a connection it goes into somekind of loop. It first gives me a security warning stating it wants to connect to the connection broker, then I get a certificate error from the connection broker, which is correct
in this case, I choose to ignore the certificate warning and continue anyway. RDP then continues; Securing external connection, checking bandwith, starting the external connection. And there it hangs, it doesnt go any further and tries to connect for ever.
The external adres of the gateway is xxx.xxxx.nl and internally it xxx.xxxx.local not sure if this could be related. I noticed an article with a powershell script that would change the .local into .nl
Strange thing it worked before. I even went as far as  trashing all 3 machines, removing the roles and removing them from the domain to run the install again on fresh machines with new DNS names. Still no luck.
Not sure on how to troubleshoot this any further. Eventlogs on the GW and CB show nothing special, no errors. One thing that I do notice is a recurring WMI 5605 ID - The root\cimv2\RDMS namespace is marked with the requiresEncryption flag. Access to this
namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.
Thanks for any thoughts on this.
Best regards,
Louis

Answer 1

HI,
Can you confirm everything works internally and your problems occur when trying to access resources externally.
Firstly check the certificates and ensure you have configured self signed or trusted.
Try turning of certificate authentication for testing only - this will answer your authentication level question.
Have a look at the following post:
http://ryanmangansitblog.com/2013/03/10/configuring-rds-2012-certificates-and-sso/
It does sound like you are experencing issues with the Internal and external nameing of the gateway. There are a few ways round this. TP has written a script which will assist with the change.
http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80/file/103829/2/Set-RDPublishedName.ps1 If you have questions
around the use of this, reply in this post.
Ryan Mangan | Ryanmangansitblog.wordpress.com | Help keep the forums tidy, if this has helped please mark it as an answer