Windows Forum

Ask something
Discussion Locked

NT 4.0 Terminal server problems

0 helpful
9 replies

by gskiaker

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Our company has two locations. We have a dedicated ISDN line with two CISCO-802 ISDN routers connecting the two locations to create a WAN. One PC at the main site is set up with Windows NT 4.0 Terminal Server, where some of the users from the remotelocation log in to run a database application. Everything has been working just fine for several years, but suddenly last week the remote users could not log into the Terminal server. The message they get is: ?The Client could not connect to Terminal Server. The server may be too busy. Please try connect later.? I have no problems connect to the terminal server with a client locally over the LAN. The remote users have no problems accessing mapped drives on the PC acting as Terminal Server, or any of the other servers. The phone company have checked the ISDN line and found them OK. CISCO cannot find anything wrong in the routers either. I even reformatted the Terminal server?s hard disk and reinstalled Windows NT Server & terminal server. Also tried a new NIC.
Does anyone here have this happen to his or her Terminal server setup, or know what could cause this sudden connection problem?

Thank you,

Gus Skiaker
Titan Inc.

9 replies

by timthetoolman

Hi,

It sounds like a licensing problem. If you're accessing TS over the LAN then make sure you're using a non-administrator account to check with.

Check the event log on the TS machine for events. If you spot an event id 52, then check the following article which is supposed to be for Win2K but may apply to you.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q258021

(remove spaces from above URL)

Cheers,
Tim.

by timthetoolman

Hi Gus,

It was blind luck I saw you replied to this. I hadn't subscribed to this post...

I guess you've already figured it out by now, but you add Terminal Services Licensing server through the Add/Remove Programs (from memory). Its a windows component.

As far as why it started happening? Hmmm... I dont really know. Perhaps some sort of corruption happened and set it off?

I couldn't really say with any certainty.

Hope you've got it fixed!
Cheers,
Tim.

by gskiaker

Thanks for all the answers. Problems solved! Our ISP had added a new server with the same name as my terminal server, and since the first DNS was pointing to one of their servers, our clients tried to log on to their terminal server.

Thanks,

Gus Skiaker

by m.r.

Since you say dedicated I'm assuming the routers would not have been tampered with. Reloading the server was a big step. I'm thinking more along the router path though as the previous answer already suggested LIC issues. I've had many a Cisco suddenly quit for no good reason especially on ISDN. The IOS can be corrupted.

by gskiaker

Tim:

Thanks for your quick answer. Looks like it could be a licensing issue because I?m set up as administrator and it worked fine. I installed the client on a local PC with a standard user login, and there I also received the Too Busy message. The licensing manager on the Terminal server has enough licenses for NT clients, but I can?t find out how to add licenses for the NT 4.0 Terminal server. How do I setup a licensing server for the Terminal server? And why did it suddenly become an issue? It worked before!

Thanks,

Gus

by m.r.

The terminal server license is tracked in a different license manager from the NT license manager. You may need to check usage count and add or revoke. Also different client types use different LIC.

This discussion is closed to new replies.