VNC and Remote Desktop Control

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

We are using a Windows 2003 Server with VNC connection for
a couple of months.

We just enable the Terminal Service on that Server.
However, since then, we are not able to connect to that
Server via Remote Desktop Connection (It says that Remote
Connection might not be enabled OR it is too busy .... ).

On the other hand, when we attempt to connect via VNC, it
gives us the following error message:
Connectoin aborted (10053).

Is it a known problem and your advice is sought.
 
Paul said:
We are using a Windows 2003 Server with VNC connection for
a couple of months.

We just enable the Terminal Service on that Server.
However, since then, we are not able to connect to that
Server via Remote Desktop Connection (It says that Remote
Connection might not be enabled OR it is too busy .... ).

On the other hand, when we attempt to connect via VNC, it
gives us the following error message:
Connectoin aborted (10053).

Is it a known problem and your advice is sought.
Click to expand...

If it is a known problem then it is specific to your
installation. Both products work quite nicely when
configured correctly.

To test each product, you should turn of the host's
firewall, then issue these commands from the
Command Prompt on a client PC on the
***internal*** network:

telnet YourHost 3389 (for Remote Desktop)
telnet YourHost 5600 (for WinVNC)

If you do not get a response then something
in your network is blocking your packets. Use
a tracer such as Ethereal to find out what's going on.
 
Back
Top