Remote Desktop Connection Lost
Up until approx a week ago, all my computers could remote into each other. Since adding a "WHS Vail" test computer to my lan, I cannot remote in to any computer. Thinking that the test rig was at fault, shut it down, but still no remote access. So checked that remote desktop was enabled on all systems, it is. Next, tried using "ping" from each system to all others on the lan. No problems, ping tests were successful. Shut down network & rebooted each device as per providers instructions starting with the modem, followed by the router then each system. Checked firewall settings on each system - no problems found. Retried ping tests & again no problems found. However, still no remote desktop connection from any system. All systems running Windows 7 Professional 32 bit with one running Windows 7 Ultimate 64 bit. Advice on how to proceed next will be much appreciated.
September 20th, 2010 3:31pm

Whattype of error are you getting? Can't find computer at all? Are you using the DNS name or IP address? Double-check your router to make sure he's not blocking any ports by chance - 3389. Not sure how you are running the application, try Start, Run, "mstsc /v:computername or ip address" Try visionapp see if you have the same issue just for fun.Charlie Hawkins
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2010 4:11pm

Sorry for the delay in replying, been busy. After attempting rdp, getting the following in a dialogue box: - 1: Remote Access to the server is not enabled 2: The Remote Computer is turned off 3: The Remote Computer is not available on the network. Tried the mstsc tip & got the same dialogue box. I take it that visionapp is a 3rd party tool, so will search for it & try that....
September 21st, 2010 5:45am

Just tried visionapp & that returned an rdp protocol error (return code: 516) along with the same 3 as above. Find this weird as I can access all computers via the network using windows explorer.
Free Windows Admin Tool Kit Click here and download it now
September 21st, 2010 5:59am

Have you verified the ports are not being blocked on the network? When you run netstat -an from command prompt be sure port not being block on local machine: TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP [::]:3389 [::]:0 LISTENING Try the port using telnet, you may have to install telnet client, it is not installed by default in W7. telnet computername 3389 If you receive "...could not communicate with host, on port 3389...", it's being blocked somewhere. Again, verify your network is not blocking 3389.Charlie Hawkins
September 21st, 2010 9:12am

"Find this weird as I can access all computers via the network using windows explorer." Remote desktop connection uses a different port & different dependencies than Network Access/SMB Access, thus Charlie is correct in that it could be a firewall blocking a specific port or service from running/connecting remotely.
Free Windows Admin Tool Kit Click here and download it now
September 21st, 2010 11:02am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics