Remote Control Error

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

Guest

Hi,

I have a Windows 2000 server and I am trying to access it through remote
desktop from my WinXP Prof desktop. I know the system is not busy because
it’s only me trying to access it. I have just about turn everything on and
add components. All the setting looks the same from server to server.

I can access my other Windows 2000 servers with no trouble. I have tried to
look at the other servers and setup this one up the same way but I am
continuously getting this error. All the setting looks the same from server
to server.
Does anyone have any idea what is going on?


"The client not connect to the remote computer
Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection.â€
 
KAT said:
Hi,

I have a Windows 2000 server and I am trying to access it through remote
desktop from my WinXP Prof desktop. I know the system is not busy because
it's only me trying to access it. I have just about turn everything on and
add components. All the setting looks the same from server to server.

I can access my other Windows 2000 servers with no trouble. I have tried to
look at the other servers and setup this one up the same way but I am
continuously getting this error. All the setting looks the same from server
to server.
Does anyone have any idea what is going on?


"The client not connect to the remote computer
Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection."
Click to expand...

The terminal server service might not be running, or
perhaps it is listening on a port other than 3389.
Try telnetting to it.
 
Thanks,
This is the message I am getting when I telnet.
Could not open connection to the host, on port 23
 
Hi,
to check port conectivity on port 3389, you should type:

" telnet $your_server_name 3389"

If you get something like " Connecting To $your_server_name ...Could not
open connection to the host, on port 3389: Conn
ect failed" , it means that your Remote Desktop connection is not accessible
because of network restrictions.

If you get black screen with flashing cursor, it means the port is open and
you should investigate the Remote Desktop configuration ( restrictions on
RDP protocol ... etc. )

regards
Dominik
 
I also experience the same error but my server is Windows 2003 it was working
a couple of days ago and I went over the Remote settings and did not see
anything changed.
 
Back
Top