Remote Desktop Initial Connections problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I attempt to connect to a specific XP Pro machine on the same network, I
received the 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 ..."

But I can get it to work if I first open Services (services.msc) and use
"Connect to another computer ..." and connect to the remote computer, then
connect with Remote Desktop.

This is the only computer that I have to do this with, and it does not
matter which computer I am logging in to it from.

This solution works but I don't know why, and may be too complicated for the
primary person who will be logging in remotely.

Any suggestions would be really helpful.
 
I should add that although on the remote computer it shows that it is
listening on TCP port 3389, until I connect to the remote computer through
Services, the computer I am connecting from shows that it is not listening.
 
Is the "Terminal Services" service set to start automatically?

http://theillustratednetwork.mvps.org/RemoteDesktop/Images/Services-TerminalServices.JPG

Check the dependencies to make sure those services are started. Also check
the event log for clues...

--

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...
 
Terminal Services is running and I couldn't find anything that seemed related
in the Event Log.

But I just found a solution using "net use \\computerName /persistent:yes".
I'm still not sure why I needed to make the connection using "net use" but it
works.


Thanks for your suggestions.
 
Back
Top