Discussion Locked

Remote Desktop will not work on internal network

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm trying to use RD to connect to my desktop from my laptop. I get an error: Could not connect to remote machine. This happens with firewalls turned off and remote desktop enabled. I also created a password protected account on the machine I'm trying to access. So then, I wen't into my Linksys Router and turned port forwarding on for port 3389 - it sends to the desktop IP address. Any ideas? I really need this to work. Works fine in the office, just not within the home network. Thanks

13 replies

by rcolon

I would attempt to run a sniffer on the LAN and see whats going on.

Ethereal is a good sniffer.

by georgeou

Open a command prompt with

Start
Run
cmd

Then type the following command.

telnet IP-of-destination-computer 3389.

If RDP is working, you will get a blank screen, if it's not, nothing will happen.

Also note that everything has its own firewall these days. XP has a firewall. VPN software have their own firewall. Antivirus solutions have their own firewall. The list goes on.

by tom friedriks

Thanks to George for the suggestion. That's good port probing test. Just a minor add. You will get nothing if port is open. Though if you'll connect to http service port and sent Return, you'll receive a code 400 on your screen. If port is closed you'll receive message that connect was failed. For cases when you have firewall installed between your LAN and outside network there is a trick how to manage to get service working on one server within a LAN seen from the outside. You can setup a port forwarding service. For example we use desktop management solution from Scriptlogic that we use not only for managing desktop clients throughout LAN but also for remote management. [url=http://www.scriptlogic.com]Desktop Authority[/url] has a very nice remote management feature and it had to be a shame if we would not use it. So we managed to build port-forwarding and redirected port on a firewall to a port on our server where sits our management service. That's was very helpful for us because now we can watch for the state and manage environment even during the vacations with notebook and browser. The best feature is that it has group policy and active directory management, so the process of user management is that as simple as it is normally within ADU&C and GMPC snap-ins.

by jshoe85

THis is all internal, I will not be connecting outside of the LAN, I just have 2 Pc's in the LAN thta I wan't to use remote desktop with.

by jshoe85

2 Computers, and a Linksys router, all firewalls are turned off, all antivirus is turned off, port 3389 is forwarded on the router to the desktop pc

by now left tr

OK - this may be incorrect but I'm sure that the receving end must be XP Pro, not Home. If they are both Xp Home the RDP will not work. If this is the case get a copy of VNC Server and Viewer from the web (it is free) - install and use it.

by georgeou

My test is for internal LAN and you should give it a try. It will tell you if the port is being blocked by some other software or not or if RDP is disabled.

by jshoe85

THey both are Home. Is it really true the recieveing end must be Pro? Because it allows you to enable both Remote Desktop and Remote Assistance in Home.

by tuktaktim

the computer that's remote has to be running xp pro .... pcAnywhere would work as well as vnc

This discussion is closed to new replies.