We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


Win 2000 Terminal Server Stops Accepting Connections

Medium Priority
Last Modified: 2013-12-05
Hi All -
I have a Win 2000 server that has been running fine for past 6 months (it was an upgrade to an older server with same applications running for 3 years) - it acts as a Terminal Application Server running a legacy MS Access application and Outlook. Typically we have about 5-10 users logged in at one time from various locations worldwide. We have a TS license for 15 people (but licensing has never seemed to stop clients from connecting as most are XP clients)

For some reason this past weekend, we started experiencing a problem where the server stops accepting connections. When we try to connect, the connection times out and just cannot connect to server. I do not have specific error at this point but will post followup when it happens again. Anyone with existing connections when this problem kicks in does not seem to be affected - their session stays going. We can log in from console no problem. Perusing the event logs has not shed any light so far.

Does this ring any bells. Where would I start to look?

Many Thanks
Watch Question

Have you configured terminal server licensing yet? If not, it will stop working after 180 days.


"Terminal Services starts looking for the license service as soon as it's installed. It also has a 90-day grace period, so that if it doesn't find a license server, it will continue to run for 90 days. But at the end of 90 days, if no license server has been found, unlicensed clients will not be allowed to log on to Terminal Services."


Yes - the license server has been configured and running no problem for 6 months.
If you go to administrative tools and open Terminal Server Licensing, does it show the server and the activation status?


Yes - it is active.
Go to in administrative tools to Terminal Services Configuration, then Server Settings. Try changing the terminal server license server discovery from automatic to "use these license servers" and put in the name of the license server.


I went there, but no  "discovery" setting - only have:
 Terminal Server Mode (Application Server)
Delete Temp folders on  exit (yes)
use temp folders per session (yes)
internet connector licensing (disable)
Active desktop (enable)
Permission Compatibility (Windows 2000 users)

Thanks  - Ford
I may have been a little off on some things, since my terminal servers are all 2003 now. If I have some time tonight or tomorrow I'll fire up a test server with 2000 & make it a terminal server so I can help more.

In the mean time, Try this to set the preferred license server:

And this to try activating the licenses again online:

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
I ended up rebooting firewall and Terminal server and seems to have fixed itself  - thanks for the response anyway.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.