If some of you recently tried to publish RDP protocol through TMG server, and suddenly lost the possibility to perform TS connections to the TMG server itself, you may find this post useful!
In TMG 2010, a System Policy rule exists allowing RDP traffic from a white-list of workstations to the TMG server itself.
Thanks to this, it’s generically possible to connect to our TMG server from allowed PCs.
If you perform the following command, you’ll be able to see the TCP listener bound to the Remote Desktop Services (RDS) service accepting incoming RDP connections on default port 3389:
Netstat –ano | findstr :3389
Now, let’s assume that you have to publish RDP protocol externally through TMG, so that TS connections from external devices toward an internal server can be established, while the internal server’s IP address is masked.
You can do this by creating a specific “Non-Web server publishing rule” in TMG:
If you run again the netstat command mentioned above after you performed this configuration, you will see no differences at all, and everything should be working as expected.
Let’s now assume you have to reboot the TMG server.
After the reboot, if you run the netstat, you’ll see that the situation has changed:
Now the TMG server is listening for RDP connection only on the IP address which has been configured within TMG’s Server Publishing rule. Moreover, we can see that the listener is now associated to the PID of the FW service itself, and we no longer have entries related to the RDS service.
If you test TS connectivity to the TMG server from one of the allowed internal workstations, it will now fail.
This happens because of a socket conflict generated between the FW service and the RDS service, and it is an expected behavior.
In order to allow remote access while publishing RDP, basically 2 solutions exist:
You can publish the RDP server on different port than 3389, using non web server publishing rule and creating a “customized” RDP protocol for the new considered port.
You can just change the RDS on the TMG to listen on a different port or adapter
To apply this second solution, you can open Remote Desktop Session Host Configuration > Right-Click on RDP-TCP > Network Adapter > then select the internal NIC.
After this action, just restart the RDS service.
If you now run a new netstat, you’ll see the following situation:
You will now have the RDS service listening on the IP addresses bound to the internal NIC, while the FW service is listening on the external side for RDP publishing.
With this configuration, it’s again possible to establish TS connections to the TMG server even when the server publishes the RDP protocol.
As always…I hope you can find this useful!!
Daniele Gaiulli Support Engineer – Microsoft Forefront Edge Security Team
Philipp Sand Sr. Support Escalation Engineer – Microsoft Forefront Edge Security Team
The second solution works great ! thanks
thanks for this, it helped me alot.
Very helpful - I was wondering what happened after this month's patch Tuesday & reboot.
I had published a couple of machines via RDS in between reboots.
TMG 2010 with 3 network cards. Second solution worked like a charm.
Thank you very much!
Creating a RDP rule worked for me; Thanks !
Thank you !!!!!!!!!!!!!!!!! helped a lot