Problem connecting to Terminal Server

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

Guest

Hi all..

This is the scenario:

1.- A computer with Windows Server 2003 Standard Edition connected to
Internet by mean of ISP A

2.- A second computer with Windows XP Professional and Terminal Services
Client installed. This computer is connected to Internet by mean of ISP B.

The problem is that I couldn't establish that remote connection. When client
tries to connect (using the server IP), it shows the following message:

"The client could not connect to the Terminal server. The server may be too
busy. Please try conencting later"

What may be happening? I tried by disabling Windows Server 2003 firewall and
it didn't connect either. May be an ISP issue? or some configuration is
missing? I tried by connecting with Remote Desktop Connection that comes with
Windows XP but the same happens.

Thanks a lot in advance
Jaime
 
1. Terminal Server Installed or Remote Desktop for Administration Enabled.
2. Firewall or ISP not blocking TCP Port 3389.
3. Is the server directly connected to the internet, or is there a NAT
device (router or firewall) inbetween? If there is a firewall you need to
open port 3389 on that device to the private IP Address of the server, then
address the public address with the Remote Desktop Client.
4. Can you open an RDP session to the server from the server's console,
i.e. on the server's console open remote desktop and try connecting to
127.0.0.1, or the NetBIOS or FQDN.
5. Any errors in the server's event log when you can't connect?

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
 
Back
Top