RD Connect Problem

[craigm]

I have several remote home users connecting to their
office desktops. One employee cannot connect with their
laptop, but can connect with other home PCs. The laptop
is WIN XP Home. The laptop worked for several months
without problem, but the user had to restore their system
with their Recovery CD. After that,he cannot remote in.


His RD software works, I can remote into local PCs on a
network.

When I start the RD, and try to connect to the office
systems, I get the following message: The client cannot
connect to the remote computer. Remote connection might
not be enabled or computer might be too busy to accept
new connections.

Any new suggestions would be appreciated.

 

[Bill Sanderson]

After restoring the system with the Recovery CD--did they also re-apply all
critical patches, via WindowsUpdate? In particular, was SP1 applied?

You say that he can RD from this machine to others on a LAN.

What's involved in the desired connection from home to work?--i.e. is there
a VPN connection as well?

 

[CraigM]

Thank you for your response. All critical patches have
been applied, I reinstalled SP1 myself. No VPN
connection involved. I called Toshiba to find out if
there was anything quirky about this laptop, uninstalled
NAV and Quicken (Quicken wants to do some Internet stuff
every time it starts up), got system to plain vanilla.
Since I can RDP to other systems on the LAN, RDP is
good. It's almost like certain addresses are being
blocked. As a regular user of RDP, the error message
comes up very quickly, immediately. I have been trying
to connect out via my DSL line, other systems on our LAN
can connect with RDP to the address we want to remote
to. The laptop's owner has a home cable connection, with
two other desktop systems. Those systems can remote into
his office. I feel it's something on this laptop. Any
ideas?

 

[Bill Sanderson]

The only other thought I have is an issue of MTU size.

I would think that this system would be at a standard 1500 after the
Recovery Disk procedure which I think is a clean install??

So--I don't see how this would be an issue unless a lower MTU were needed
for something like a PPPoE ADSL connection.

Since the user is on cable, the standard 1500 should be right, I think.

You could perform MTU testing using Ping between the home client location
and the particular work IP involved and see what happens.

This article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314825

tells how to use ping to detect whether a lower MTU is needed for a given
connection.

Your description of the connection path involved wouldn't lead me to say
that an MTU issue might be involved--I'm not clear whether there is DSL
involved--but it isn't a hard test to do--just do some pings as directed in
the article, starting with 1472 and working down,