Work to Home Computer "Remote Desktop Disconnected"

[Guest]

The following error occurs when I try to connect from my work computer to the
home one: "Remote Desktop Disconnected: the specified computer could not be
found. Verify that you have typed the correct computer name or IP address,
and then try connecting again."

This is what I've done so far:

At home: Turned off all firewalls except for the Windows firewall. The
windows firewall has the "exceptions" turned on and the "Remote Desktop"
checked. The home computer has DSL internet access via a Speedster modem. The
computer is on and connected to the internet but may slip into Standby mode.

At work: The Remote Desktop Connection is downloaded on the laptop at work
which is connected to the internet via a LAN. I put in the computer name and
press connect.

Did I miss anything?

Thanks,

James

 

[Sooner Al]

Any chance the DSL modem (Speedster) is also a router? Run the "ipconfig" command on the home PC. If
it reports an address in the 192.168.X.X range then you need to contact the ISP or look at the
manufacturers web site for help opening TCP Port 3389.

Otherwise, configure the PC so it does *NOT* go into standby/hibernate and test again.

Make sure in all cases your calling the correct IP address...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Leythos]

At work: The Remote Desktop Connection is downloaded on the laptop at work
which is connected to the internet via a LAN. I put in the computer name and
press connect.

Did I miss anything?

Did you ask the IT staff if they allow connections using RD outside the
network, most companies block outbound connections like that - it's a
security risk.

 

[Bill Sanderson]

The main thing you missed, as Al mentions, is that you must use the WAN IP
address of the home router.

You may also have the issue Leythos mentions--outbound restrictions at work.

And, lastly, a number of network drivers don't work properly when resuming
from suspend--so for testing purposes, I would recommend setting power
management to not allow the machine to go into standby.