I installed a 2008 Standard Server with TS or Terminal Services and all appears to work fine from within the LAN's browsers using XP machines with Srvpk3 and Vista machines w/Srvpk1. However, despite opening up ports 3389 and 443 on the firewall, I am still unable to access the TS from the internet? Has anyone come across this TS inaccessibilty issue from the internet and resolved it?
Microsoft Server OSWindows Server 2008
Last Comment
isprofessionals
8/22/2022 - Mon
brittonv
Are you using real, routable, IP's behind your firewall (not 192.168.x.x or 172.16.x.x, etc.)
If not you need to NAT an IP from your public IP's to the Private IP that your TS is running on.
Kieran_Burns
you also need to open nbname on the firewall
I really can't believe you're opening TS to the world though. Really not a good idea.
You'd be far better off (security wise) creating a VPN client Server and having the remote clients authenticate on that and then TS in through the client tunnel
There are very simple ways to enhance TS security and still allow RDP access over the Internet. I am still to see a TS that was hacked over the Internet. And this is what I have been doing for a living in the past 14 years. TS/Citrix only.
I assume you are trying to connect to the external IP address of your firewall on port TCP 3389. Is that the case?
Unfortunately, I didn't receive the solution I was seeking which was to securely access TS from outside/externally. What I did was enforce the usage of a VPN connection from the outside to the inside first and then had the employees use the terminal server via remote desktop. I hope this helps.
If not you need to NAT an IP from your public IP's to the Private IP that your TS is running on.