cannot connect, do I have to open a port in the router?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have just installed windows 2003 at work and all is fine except the remote desktop. I can use remote desktop from within the office using the ip address of the server but I am unsure how to access from home going through a router. Do I have to open a port on the router and if so which one? Any help would be appreciated.
 
When i looked at the settings for the router that port was already properly pointed to the ts. What is the right format to input the address. Would it be xxx.xxx.xx.xxx:3389, with the x's being the i.p. address? I tried from within the office with no success but thought that it might only work from the other side of the router so I left and tried from my home computer but with the same results. ANy help would be appreciated.
 
There's no need to specify the port number, like you would in a URL. When on the private local network, using the Firewall's WAN IP Address should timeou

Here's a screenprint of a customer's linksys router setup
http://www.workthin.com/images/LinksysPortForwarding.JP

On the private network you'd address the Remote Desktop Client like
Start -> Run -> mstsc -> PrivateIpAddress, i.e. 10.0.0.5 (or whatever the server's IP address is

Picture here
http://www.workthin.com/images/RemoteDesktopClient.jp

From the Internet you'd do
Start -> Run -> mstsc -> FirewallWanIpAddres

How tos here
http://www.workthin.com/tshta.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- snewman7 wrote: ----

When i looked at the settings for the router that port was already properly pointed to the ts. What is the right format to input the address. Would it be xxx.xxx.xx.xxx:3389, with the x's being the i.p. address? I tried from within the office with no success but thought that it might only work from the other side of the router so I left and tried from my home computer but with the same results. ANy help would be appreciated.
 
Still no luck .When I type in the address of the connection a message comes up saying "THe client could not connect to the remote computer". "Remote connectons might not be enabled etc".
I know remote connections are connected and working as it works fine frm within my office using the internal ip address of the TS, and I know that the ip address of the router is right as I use a telnet program to access the router from home for another application. Where do I go from here?
 
So your setup is "exactly" like this:
Internet Computer using Remote Desktop Client 5.2 -> Addresses Router WAN Interface Public IP Address -> Router set to forward TCP Port 3389 Traffic from the Internet to the Static Private IP Address of the TS, i.e. 10.10.10.5

Feel free to email me a screen shot of your router's port forwarding, client's Remote Desktop Connection & Server's IPCONFIG and I'll tell you if I see something wrong. Don not to publish this info on a newsgroup.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

----- snewman7 wrote: -----

Still no luck .When I type in the address of the connection a message comes up saying "THe client could not connect to the remote computer". "Remote connectons might not be enabled etc".
I know remote connections are connected and working as it works fine frm within my office using the internal ip address of the TS, and I know that the ip address of the router is right as I use a telnet program to access the router from home for another application. Where do I go from here?
 
Back
Top