Re: RDP fails, XP Pro to XP Pro
- From: "Robert L. \(MS-MVP\)" <noreply@xxxxxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 10:13:33 -0500
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
"BFH" <BFH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:ECEF2C94-D78C-4837-925B-2C61203E7B5C@xxxxxxxxxxxxxxxx
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?
.
- Prev by Date: Re: RDP fails, XP Pro to XP Pro
- Next by Date: RDP works as admin but not user
- Previous by thread: Re: RDP fails, XP Pro to XP Pro
- Next by thread: Re: RDP fails, XP Pro to XP Pro
- Index(es):
Relevant Pages
|