XP RDP client cannot to the Terminal Server

  • Thread starter Thread starter Cheryl
  • Start date Start date
C

Cheryl

Hi Group,

I experience a problem that a client cannot connect to the
Terminal Server showing

"The connection was ended because of a network error.
Please try connecting to the remote computer again"

It is checked that the client was not able to ping to the
Terminal Server.However, they said that the ISP hasn't
blocked the usage of port 3389.

So I wonder what's the problem?
Does anyone have tried this before?

Thanks
 
If you can't ping the server from the client, then you cannot connect to it
with rdp. This is a more basic problem than port 3389 being open or not.
It sounds as if your client connects to the Internet through an ISP. How is
your server connected to the Internet? Any firewalls there?
 
The server is connected to the Internet behind a firewall
I have checked that the ping function is disabled. That's
the reason why the client cannot ping the server.

However, other client is able to connect to the Terminal
Server. Only 1 client report that error. So I wonder
where's the problem?

Thanks
 
Have you verified that port 3389 on the firewall is open?
Can you telnet to port 3389 from the client?

187628 - Using Telnet to Test Port 3389 Functionality
http://support.microsoft.com/?kbid=187628

This other client that does connect: is it also connecting from
the Internet, or from the LAN?

Have you verified that this is not a license issue?
Are there any events in the EventLog?

There could also be a black hole router between your client and
your server, in which case you'll have to change the MTU size. See
topics 4 and 7 under Connectivity in the FAQ at
http://www.microsoft.com/windowsserver2003/community/centers/termi
nal/terminal_faq.asp
 
Back
Top