Hi all
I've configured an all-in-one WS2012 Remote Desktop server with RD Gateway and RDWeb, serving RemoteApps to a distant location. The RD Gateway listens on 8388 TCP (because 443 is already taken on my NAT) and 3391 UDP. The RDWeb similarly listens on 8388.
Since the gateway is not listening on the standard port, I had to run this command http://social.technet.microsoft.com/Forums/windowsserver/en-US/6ed0845a-1a51-4c05-8331-ece9c0eb73fa/remote-desktop-gateway-port?forum=winserverTS to tell RDWeb to write the correct TCP port in the webfeed it distributes (and I am NOT comfortable with having to do it manually since the UDP port is an UI-changeable setting, but I digress...).
RemoteApps open fine from the remote location... except UDP is not used. Connections show up in the RD Gateway Monitoring as HTTP, not UDP. Also a direct MSTSC connection to the server doesn't use UDP (it doesn't appear in the signal bars text).
But I am sure that:
1) public address's port 3391 is correctly UDP-mapped to the Gateway, tested with network monitor
2) the TS is listening on UDP 3389 (RDP) and 3391 (RD Gateway), tested with netstat
3) my Win7 client uses UDP when connecting to other Win8 workstations at my company, and these Win8 clients won't use UDP when connecting to the TS
4) even though UDP is not used, I see packets in the network monitor, coming and going to port 3389
What can I do to address this?
I have two more questions.
1) I'm inclined to think that for full UDP usage, remote NAT'ted client would need to be in a DMZ, otherwise how are they going to receive UDP packets coming back from the server?
2) Unrelated to this: the Best Practice Analyzer in Server Manager found that the RD Gateway certificate is invalid; needless to say, other parts of the same Server Manager (RDS > Collections > Edit Deployment Properties > Certificates) think otherwise, so does the RD Gateway manager. God fashioned panels...
Thank you for any answer...