lost abillity to login

[Kenneth Westby]

Greetings all,
I ran into a bit of a problem last week that I can't figure out.
Running Windows 2000 Server, SP4, all of the latest patches and hot fixes.
I use Terminal Services to occasionally login from home to fix minor
problems or restart the server. I now have lost the ability to login. It
doesn't matter if I try to login from home, or from another machine located
in the data center next to this server, no ability to login. I can log into
all of the other servers if I am in the building, but because this server is
my domain controller, I can not login to any of our other servers from
outside the building. What does it entail to restore my ability to login
remotely?
Thanks much for any and all replies.

Kenneth Westby

 

[Vera Noest [MVP]]

Which error message do you get when you try to connect?
Is it a username/password/permission problem, or is the server not
allowing rdp sessions/not listening to port 3389?
Can you telnet to port 3389 of the server?
Can you logon to the console of the server?
Can you remotely view the EventLog of the server? Anything there?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Kenneth Westby]

Hi Vera,
The header of the window is: Terminal Services Client Disconnected. In the
window is: The connection to the server has timed out. Try connecting to
the Terminal Server again.
RDP is listening to port 3389
I can only log on at the server (physically)
I'm sorry, I have heard of telenet connections years ago, but do not know
how to perform it. I did a search on the Microsoft support page for telenet
help and come up with only three KB articles that really don't tell much
about it.
Will sift through the log to see if there is anything there.
Thanks much.

Kenneth Westby

 

[Vera Noest [MVP]]

OK, so you never get to the login dialog box.
Since you can logon locally to the console of the server, check the
EventLog for any errors.
Also run Terminal Server Administration and check if the listener
session isn't "down" (under "Status").
Run the command netstat -a and check if the server is listening on
port 3389 (since you can logon to the console, this is easier then
using telnet to port 3389, so forget about that).

Can you ping the server? Verify also that the network card is
functioning.
More troubleshooting tips here:

186645 - Troubleshooting RDP Client Connection Problems
http://support.microsoft.com/?kbid=186645

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Kenneth Westby]

OK,
Checked the event log, nothing listed for terminal services errors.
Yes I can telnet to the server. Just have a blinking curser on a blank
screen.
I'm not running terminal servers in a licensed mode, but rather the mode
that allows you to connect with a limited number of remote sessions.
Typically, I am the only one that connects to the server remotely,
therefore, one session at a time. Si I didn't find a "Terminal Server
Administration" to check the listener.
I did run netstat and port 3389 is listening.
The server can be pinged from all clients in the building.
Both NIC's are functioning properly.