![]() |
Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us| |
|
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. Case 1. The user has disabled Windows firewall. Try to telnet port 3389 from remote computer, receive failed error. Then try access itself using Remote Desktop, receive the same error. Finally, we find it is MacAfee personal firewall blocks the port 3389. After adding TS/RDC service (port 3389). The client can access it. Case 2. The user uses Norton security and open the port 3389. The LAN users can access Remote Desktop computer but not not VPN clients. After checking the Norton Security settings, we find the firewall allows only local IP range 192.168.0.x to access the RDC while the VPN client is assigned different IP range 192.168.1.x. It works after adding 192.168.1.0 subnet to the Norton Security. Case 3. The user is try to access a Windows 2000 Pro. Resolution is installing VNC or NetMeeting. Related Topics Connection to remote computer was broken caused by network error
Troubleshooting terminal server issues
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2007
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.