W2K RDP not listening and no console access

  • Thread starter Thread starter Toby
  • Start date Start date
T

Toby

I have a W2K server running Terminal Services (in administration mode)
but it does not appear to be listening on the RDP-TCP port, and
therefore client connections are not possible.

To complicate matters, the video card in the server has failed and I
cannot even gain console access to check the problem.

However, I have a Windows 2003 Server in the same domain which is able
to remotely access the resources of the W2K server, but when I run
Terminal Services Manger from the 2003 machine and browse the W2K
machine, I do not see any RDP-TCP protocol entries against the W2K
machine.

As I can remotely access the "Services" of the W2K machine, I can
confirm that the Terminal Services service has started correctly. I
can also remotely access the Event Log, but this doesn't have anything
relating to the failed client connections.

Any ideas? Is it possible that because the local video card has failed
that this is someone preventing Terminal Services from operating (i.e.
is Terminal Services dependent on the local video card?).

I've read several of Microsoft's KB articles on the subject, but since
I cannot gain console access to the server, I'm kinda stuck.

Thanks.

Toby.
 
Hi,

First of all.

Use Computer Management console on the Windows 2003 server and remotly
connect to the Windwows 200 server. (Right click on Computer Management
(Local) and select "connect to another computer") Thsi will give you access
to services running on Windows 2000 computer, check if Terminal Services are
running.

Tahir Saleem
Citrix User Group Norway
http://www.cug.no

Citrix User Group Sweden
http://www.cug.se
 
Back
Top