RDP fails, XP Pro to XP Pro

[Guest]

I have two XP Pro (SP2) computers, on the same LAN (no intervening router or
firewall), and am trying to do remote desktop from PC-A to PC-B, and it's
failing. When I try, I get the generic "Client could not connect... might
not be enabled... might be too busy... ask administrator" message.
Unfortunately, I'm the administrator. Here's what I've checked so far:
- "allow users to connect remotely" is checked on PC-B
- I've disabled and reenabled it, and rebooted
- I've attempted to connect via NetBIOS name, FQDN, and IP address.
- I've looked at services running on both PCs (PC-A is able to accept RDP
with no prob) and they look identical. But everything marked "automatic
start" is running.
- Windows firewall is off.

I'm stumped. What should I look at next?

 

[Sooner Al [MVP]]

I have two XP Pro (SP2) computers, on the same LAN (no intervening router
or
firewall), and am trying to do remote desktop from PC-A to PC-B, and it's
failing. When I try, I get the generic "Client could not connect... might
not be enabled... might be too busy... ask administrator" message.
Unfortunately, I'm the administrator. Here's what I've checked so far:
- "allow users to connect remotely" is checked on PC-B
- I've disabled and reenabled it, and rebooted
- I've attempted to connect via NetBIOS name, FQDN, and IP address.
- I've looked at services running on both PCs (PC-A is able to accept RDP
with no prob) and they look identical. But everything marked "automatic
start" is running.
- Windows firewall is off.

I'm stumped. What should I look at next?

Can you ping PC-B from PC-A using the local LAN IP for PC-B?

If you run the "netstat -a" command on PC-B does it show the computer
listening on TCP Port 3389?

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

--

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...
How to ask a question
http://support.microsoft.com/KB/555375

 

[Robert L. \(MS-MVP\)]

Can you telnet port 3389? Or these links may help.

Terminal Services client disconnected
The client could not connect to the Terminal server. The server may be
too busy. Please try connecting later. Event ID 52 - Description: Object
Name not ...
www.chicagotech.net/remoteissues/eventid52.htm - Similar pages

The client could not connect to the remote computer
"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. ...
www.chicagotech.net/remoteissues/sbsrww1.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

 

[Guest]

Thanks to both - both of you helped a lot. Turned out to be a WINS/DNS
thing. PC-B was using an address that was still in WINS as belonging to
another PC- I was sloppy in not checking PC-B's address and what PC-A was
resolving as PC-B's address. Working now, thanks.

 

[Robert L. \(MS-MVP\)]

Thank you for the update.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com