There are many possibilities. Normally, I will use telnet to check the port 3389 first. this case study may help,
Case Study - The client could not connect to the remote computer
Symptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are prevent your connection.
http://www.chicagotech.net/remoteissues/rdc2.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
"Boe" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hello,
I have several clients using Windows XP SP2. I've checked their systems.
They are using Windows firewall but remote assistance, remote assistance -
windows messenger and voice and remote desktop are all checked.
However I can't get in on half of them. Even if they turn off their
additional firewalls such as McAffee or BlackIce. Any guess on why their
computers won't let me in when they initiate a remote assistance request -
my computer just stays at connecting until it eventually times out.