LAN-Remote Desktop Connection Problem

gpern83

n00b
Joined
Aug 23, 2005
Messages
25
Hello,

I am trying to connect to my webserver, running 2003 standard, from my workstation running XP pro. I can connect to my application server(2003 SBS) just fine, and both are on the same domain, but keep getting an error when trying to connect to the webserver. Remote desktop is enabled, and since its on the LAN, running only through a switch, there shouldnt be any other settings right? Since I am an admin, I should already have RDP rights, shouldnt I? Windows firewall is not enabled.

Error Message:

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are precenting your connection.

Please try connecting again later. If the probme continues to occur, contact your admin.


Any thought or suggestions are greatly appreciated.

Garrett
 
Make sure you enable RDP. It's not on by default.

Control Panel > System > Remote > Enable Remote Desktop on this computer
 
Thanks for the reply.

Yes, RDP is enabled. I even tried unchecking, then restarting, and re-checking it. I cant come up with anything on this. I have tried connecting to the server using its IP address, and the computer name. Same outcome. I am not going through a router. All the computer are on the same domain, and none of them have a firewall that would fall into place. The only firewall is hardware, and its outside the loop.

Garrett
 
Double check your group policies. SBS defaults to enabling the firewall on all machines except the SBS machine.
 
I have checked through the policies, and everything appears to be fine. Are there any steps I can take to narrow down the problem?
 
Ok.. Here is a little more information. Hopefully some kind of indicator. I am able to login via RDP through WAN, but not LAN. How can this be?
 
Ok.. Here is a little more information. Hopefully some kind of indicator. I am able to login via RDP through WAN, but not LAN. How can this be?

Double check the internal ip that you are trying to connect to.
 
If your trying to use the external IP or a hostname that resolves to it that would likely be the problem. When you do port forwarding those are only applied to packets coming in the external interface, and even though you are using the external IP, those don't get applied (unless your router is configured in a special fashion which would likely cause connections to it's internal IP to get the same forwarding).
 
If your trying to use the external IP or a hostname that resolves to it that would likely be the problem. When you do port forwarding those are only applied to packets coming in the external interface, and even though you are using the external IP, those don't get applied (unless your router is configured in a special fashion which would likely cause connections to it's internal IP to get the same forwarding).

Try using your external ip inside your lan.
 
Logging in with username Administrator?
Is this server actually joined to the domain?
Can only connect from the inside using the public/external IP address if your router supports "loopback"....which most lower end routers do not.
 
Logging in with username Administrator?
Is this server actually joined to the domain?
Can only connect from the inside using the public/external IP address if your router supports "loopback"....which most lower end routers do not.

Dude my Linksys WRT54G has loopback, so do most routers, even the "low-end" ones.

This machine does not have to be part of the domain, he does not have to login with administrator either.


He stated that he can login remotely just fine, but he cannot login when he inside the network. He must either be using the wrong internal ip (or hasn't tried using the external) or he is trying to use some sort of hostname that is not resolving correctly inside the lan.
 
Back
Top