Error connecting to Terminal Server 1

[powahusr]

Does anyone have any idea why some people at my work cannot connect to a system through Terminal Services while other folks can? When I try to connect to the server, I receive the following message: “Error connecting to Terminal Server: xxx.xx.xx.xxx” The servers are part of a Workgroup which includes other systems running Terminal Services. Users also receive the same error message when connecting to the other systems too. Clients trying to access these servers are part of a Windows Domain.

Here are some pertinent details about the systems in question:

O/S: Windows 2000 Server
I can ping the systems in question and access their share’s
The Configuration of each server has not changed
Each Server is configured for DHCP

Clients’ info that try to access these systems:

Microsoft Windows 2000 [Version 5.00.2195] (SP1)
IE Version: 5.00.3103.1000
DHCP is enabled

 

[ianf]

My first stop would be to check that all my licenses have not been used up in Terminal Services Manager. If they have, but there are disconnected sessions still holding licenses you could reclaim them to temporarily solve the issue. Ian

"IF" is not a word it's a way of life

 

[powahusr]

Ianf,

Thanks for the info; it does seem logical that this may be a licensing issue. I looked in both Terminal Services Manager & Terminal Services Configuration and could not find anything that reflected licensing. I'm not all that familiar with Terminal Services; can you please shed some light on this?

Thanks

 

[Guest_imported]

you need to make sure that your Terminal Server License is started. Go into services scroll down till you see Terminal server licenses and start it if it has stopped. I have had this problem before with one person being logged on and others at other sites cannot. Also check if any of the people are dial ups by chance you have to set the DNS and Winns for them.....YOu can also look up the licenses through Control panel or through Start/'Programs/admin tools/licensing....

 

[ianf]

Powahuser,

If you navigate to
Start>Programs>Terminal Cervices Client>Terminal Services Manager
you'll see all your servers and all the sessions that each Terminal Server is servicing, both active and disconnected.

In the right hand window you can see tabs to view each server by user,session,process or info.

Within those windows you can select a user, connection or process and kill it if you want to.

What I've found is that the message you've described probably means that you have a lot of disconnected or idle sessions that are still holding licenses just in case the client wants to reconnect in the near future.

You can kill these to free up the licenses. All this will do, as far as I know, is force the user to go through a full login into the terminal Server session again to gain a new license.

I'm sure there must be a time-dependant "revoke dormant license" kind of a registry hack somewhere but I haven't found it yet.

Hope this helps Ian

"IF" is not a word it's a way of life

 

[powahusr]

Thanks all for your helpful replies!