Terminal Server will not accept any connections

[etdit]

Good Morning,

I have a client that is running a Windows 2000 Server with Terminal Server. Last weekend they lost power and when they rebooted the server, no one can connect via TS client.

I have run the client from their two workstations to connect to Terminal Servers outside of their office and there is no issue. So I have ruled out the clients (workstations).

Everything on the Server appears to be working fine, but for some reason we can not connect to the server via Terminal Server. When checking licensing on the server, it indicates that they have Unlimited Licenses.



Any thoughts or ideas are greatly appreciated.

 

[t3hseen]

try this: go to Control Panel, Open "Network Connections", Right click on your Local Area Connection that is connected. Go down to "TCP/IP", select Properties. When the power outage occurred the TS might have reverted to "Obtain an IP automatically" ...If that has happened you will have to enter in the values accordingingly. Also you will have to change settings in DNS. Let me know if this helps.regards

 

[t3hseen]

I forgot to say in above post you will have to check "Use the following address" and enter those values.

 

[Seaspray0]

Some service packs require a reboot before they become effective. If you have applied service packs to the TS but not rebooted, they may have activated on the reboot. Also, check the event logs to see if they can provide you with any information as to why the service isn't working right.

Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA

 

[etdit]

Thanks for the input, guys.

1. The IP Address is still set at the correct static IP.
2. No new service packs installed.
3. I will have client access the event log and see what is happening.

I do know the server boots with the 'a device or service failed to start', but I don't recall which one it is/was. Again, I'll have client review the event log and post back with what we come up with.

Thanks!
John