Networks

Ask something
Question Locked

Remote Desktop on Server 2003

0 helpful
9 replies

by dman_1092

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have Server 2003 installed with remote desktop enabled. The firewall has port 3389 forwarded to the servers ip 192.168.1.50. I can successfully use remote desktop from within the LAN by its internal ip or computer name. I am trying to use remote desktop from outside the LAN via the internet. I looked up my IP provided by my ISP. If I enter that into remote desktop I get a message saying that remote connections might not be enabled or the server might be too busy to except incoming connections. It also says that there might be network connections causing the problem. I have checked the router many times to make sure that port 3389 is enabled for both UDP and TCP for the servers ip. I have even gone as far as shutting the firewall off to eliminate that as a problem. I also checked many times to make sure that I have permissions. My log on currently has domain admin rights as well as being a member of the remote users group. I also ran the netstat -an command to verify that the port is open and it is listening. I also checked services to make sure that it is running. Is there something that I am missing so that I can remote into the server from the internet?

9 replies

by naughtymonkey

remote desktop connections, did you make sure your ID was in the User list. It is different than the Remote Users group.

Edit to add...Is port 3389 open from where you are trying to connect. And forget about the first one since you can connect internally.

by dman_1092

My id is in the list as well belonging to the remote users group. I am also a member of the remote users group.

by scott_heath

Just to make sure, the IP address from your ISP doesn't begin with 10.x.x.x or 192.168.x.x does it? Some ISP NAT their traffic to keep people from running servers from home connections. It's a long shot, but since you seem to have covered the other bases I thought I would check.

BTW, does the router have a management interface you can get to via the web? If so, does that work OK? This sounds like a home network so if the router has a DMZ option you could add the IP of your server to the DMZ and then make sure you configure a firewall on it. Not as secure, but good for testing.

by dman_1092

No My IP address in 71.192.xxx.xxx.
The router does have a web interface that I can log into. I just tried to use the DMZ but having the same issue.

by dman_1092

Thank you everyone for your responses. It turns out that filter NAT redirection was enabled on my router. By having this turned on my server would block access to the server from outside which explains why it would work internally.

by ic-it

on a registired domain and not a .local? If it is not then your ISPs (or any external DNS) can not resolve the name and the 192.168.xxx.xxx is not a routable IP address.
If it is you should be able to use the FQDN to reach it i.e.
\\Server_name\domain_name_path or
\\Server_name\MSDN-Domain.microsoft.com

by dman_1092

It is a Linksys WRT54G. I just posted a reply. I solved it. Turns out that filter NAT redirection was turned on in the router. Thanks for the help.

This discussion is closed to new replies.