Discussion Locked

Win2K Terminal Services Errors

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are having trouble getting Terminal Services running in remote administration mode on one of our W2K servers. All hot fixes, patches, and updates available from Microsoft have been loaded, and we've tried everything available on MS's knowledgebase site with no success. We've uninstalled and reinstalled TS - again, no luck. The RDP-tcp listener never initializes even after recreating the connection. Is there anything short of rebuilding the server left to try?

3 replies

by jedimaster2003

FYI.

If you are using Win2k, or xp, you could use "Remote Desktop" for this connection (free download from MS), the client is free, and remote Administration could be performed. I have at times received those errors when the client setup optionsare not correct, and\or the account on the Server, or host side is not synced up.

Hope this helps.

by aberning

No errors in any of the event logs, the clients are getting "Terminal Services Client Disconnected" - "server may be too busy" error when attempting to connect - and the RDP-tcp listener connection shows as "down" in Term Serv Manager. I found articles at MS's knowledgebase site that appeared to address this exact issue - but have applied them all with no success. Thanks for taking a look.

This discussion is closed to new replies.