Clients being kicked out of Terminal Server sessions
I am running a Windows 2000 Terminal Server in our network. I built this machine and installed all the software and then added the Terminal services component. During the first week of use everything was fine. People could log in and do their work. The second week was when people started having problems. The basic scenario is that an individual will log on and then will lose the connection after a few seconds or wont be able to log on at all.
I went into the Terminal Services Manager and saw that their were multiple instances of the same client sessions (example..John Doe with 10 consecutive sessions). I terminated these and then refreshed but the same things happens...people get cut of or cant log on and multiple sessions appear for the same account.
How do I fix this? I want to allow everyone (approximately 9 clients) to be able to logon and have a session length of at least 5 hours BUT I want the sessionn to end once the log off. By the way, I made sure they werent just closing the terminal services window without actually logging off.
I am perplexed with this problem and need help. Thank You
Best Regards
Mike
I went into the Terminal Services Manager and saw that their were multiple instances of the same client sessions (example..John Doe with 10 consecutive sessions). I terminated these and then refreshed but the same things happens...people get cut of or cant log on and multiple sessions appear for the same account.
How do I fix this? I want to allow everyone (approximately 9 clients) to be able to logon and have a session length of at least 5 hours BUT I want the sessionn to end once the log off. By the way, I made sure they werent just closing the terminal services window without actually logging off.
I am perplexed with this problem and need help. Thank You
Best Regards
Mike
ASKER
Jay_Jay70:
Thank you for responding. Where is "computer components" located?
Mike
Thank you for responding. Where is "computer components" located?
Mike
you will need to open up AD and edit the group policy....
Active dir user and computers, select the OU that they are in right click and select properties, then Group Policy tab, then EDIT button
Or on the machine that is the terminal server go to START MENU then RUN type in GPEDIT.MSC click OK or press enter
Or on the machine that is the terminal server go to START MENU then RUN type in GPEDIT.MSC click OK or press enter
Did you license the terminal server as well? If you don't have a license server running and activated then they only have access for so long and then it won't let them access, doesn't sound like this is your problem, but you will run into it pretty soon if you didn't set that up.
ASKER
Thanks for responding everyone:
I never set the Terminal Server up on the domain. It is on its own workgroup (the only one). There was a Networking contract group that installed a terminal server here before I joined this company. It was set up as a workgroup also. It had viruses,and was corrupt . I thought I had cleaned it up and fied the problems so I decided to join it to our domain. The second I did everyone would get cut off....Like the problem I am having now. So I upgraded hardware, wiped the disk clean, reinstalled windows 2000 server, added my applications and then installed Terminal services. It worked like a charm...for a week. Now I am back to it kicking people off like the old terminal server.
Isnt there a registry fix for my problem? I went to Terminal Services configuration, right clicked on the RDP session on the right pane and clicked on properties. I did not see any setting there that I could adjust to address my problem.
I have gone to group policy on the machine Terminal server. Is there anything to adjust here?
Any other suggestions?
Thank you for your help
Mike
I never set the Terminal Server up on the domain. It is on its own workgroup (the only one). There was a Networking contract group that installed a terminal server here before I joined this company. It was set up as a workgroup also. It had viruses,and was corrupt . I thought I had cleaned it up and fied the problems so I decided to join it to our domain. The second I did everyone would get cut off....Like the problem I am having now. So I upgraded hardware, wiped the disk clean, reinstalled windows 2000 server, added my applications and then installed Terminal services. It worked like a charm...for a week. Now I am back to it kicking people off like the old terminal server.
Isnt there a registry fix for my problem? I went to Terminal Services configuration, right clicked on the RDP session on the right pane and clicked on properties. I did not see any setting there that I could adjust to address my problem.
I have gone to group policy on the machine Terminal server. Is there anything to adjust here?
Any other suggestions?
Thank you for your help
Mike
ASKER
When I installed windows 2000 server, I used the product license key which we purched. Is there any other activation necessary? I am new to working with the terminal server so please excuse my ignorance.
Thank You
Mike
Thank You
Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You may already have this working, because you can't connect at all from a machine that doesn't have the proper license.. you maybe having other network problems.. but you should definetly find out about the licensing as if you don't do that no one will be able to connect when their temp. lic. runs out..
ASKER
DeadNight:
The terminal server worked for over 2 years not attached to the domain. There was no Active Driectory on the machine. It was just a part or the default windows workgroup. This I am 100% certain of. However I see where it is NOT licensed. I am going through the prompts to activate it now. I am waiting for the e-mail with some sort of key that MS is supposed to send.
I will update in a few minutes
Mike
The terminal server worked for over 2 years not attached to the domain. There was no Active Driectory on the machine. It was just a part or the default windows workgroup. This I am 100% certain of. However I see where it is NOT licensed. I am going through the prompts to activate it now. I am waiting for the e-mail with some sort of key that MS is supposed to send.
I will update in a few minutes
Mike
I don't know how it worked then, this is straight from Microsoft on Terminal Server Licensing:
http://www.microsoft.com/technet/prodtechnol/win2kts/evaluate/featfunc/tslicens.mspx and you have to have a licensing server for terminal services to work even with w2K, they changed this for w2k3 you no longer have to have it on a domain controller. Now in admin mode licensing is not necessary, but it is for application mode.
Licensing Service Location
The license service must be discoverable by the terminal servers. For a Windows 2000 domain, this means the license server must be deployed on a domain controller. This can be an existing domain controller. No separate domain controller is required simply for the licensing service. The terminal server will discover the license server by enumerating its domain controllers and checking for Terminal Services Licensing. For a workgroup or a Windows NT 4.0 domain, the license server may be deployed on the terminal server or any peer server. In this scenario, terminal servers will locate the available license server through broadcast.
http://www.microsoft.com/technet/prodtechnol/win2kts/evaluate/featfunc/tslicens.mspx and you have to have a licensing server for terminal services to work even with w2K, they changed this for w2k3 you no longer have to have it on a domain controller. Now in admin mode licensing is not necessary, but it is for application mode.
Licensing Service Location
The license service must be discoverable by the terminal servers. For a Windows 2000 domain, this means the license server must be deployed on a domain controller. This can be an existing domain controller. No separate domain controller is required simply for the licensing service. The terminal server will discover the license server by enumerating its domain controllers and checking for Terminal Services Licensing. For a workgroup or a Windows NT 4.0 domain, the license server may be deployed on the terminal server or any peer server. In this scenario, terminal servers will locate the available license server through broadcast.
Oh, and BTW all Terminal server support from Microsoft is FREE! Yep, they are trying to stick it good to Citrix for not selling them the ICA protocol that is why the licensing is such a big deal in windows 2003 and no longer free for clients.. and thus support for terminal services is FREE from Microsoft, so if all else fails, give them a call !!
(I just went round and round with them and Citrix and licensing as we are trying to remove AD from our licensing server and move to 2003, what a headace, unless you need 2003 for some reason- don't get it- what a waste of money! 2000 works and is compatibile with just about everything and still supported)
(I just went round and round with them and Citrix and licensing as we are trying to remove AD from our licensing server and move to 2003, what a headace, unless you need 2003 for some reason- don't get it- what a waste of money! 2000 works and is compatibile with just about everything and still supported)
ASKER
OK, I activated the license. After activated it asked me for an enrollment number which I have no idea what it is. I tried the activation key they sent me and the license number and got nowhere. Upon going to Terminal server Licensing I see that it gives categories there on existing windows licenses and temporary.
How do I dictate seeion time length and ensure that there are not multiple instances of the same account showing connected under Terminal server manager?
I REALLY appreciate your help
Mike
How do I dictate seeion time length and ensure that there are not multiple instances of the same account showing connected under Terminal server manager?
I REALLY appreciate your help
Mike
Don't worry about it since you are using windows 2000 terminal server, you just need a license server working and then windows 2000 and xp connect for free no CAL needed.. but you have to have one that works, find the phone number and call it they will walk you through crap and give you the codes to unlock it.
Use the phone option, it's annoying but it works...
Use the phone option, it's annoying but it works...
And if I can save you the hours upon hours of work I just had to go through to figure this crap out.. good! It's all because of Microsoft is still mad that Citrix wrote a better version of Windows NT server than they had.. they stopped allowing anyone to see their source after that... LOL
ASKER
DeadNight:
I appreciate all your help and advise. One last question. How to I regulate session time length? Also, How do I make sure that a session closes if a user shuts down the terminal services client window rather than properly logging out?
Thank You so much
Mike
I appreciate all your help and advise. One last question. How to I regulate session time length? Also, How do I make sure that a session closes if a user shuts down the terminal services client window rather than properly logging out?
Thank You so much
Mike
sorry I typed this up but must not have submitted it..
here is a shorter but to the point version of what I typed before (sorry short on time)
Active Directory accounts have a tab to set it per account.
The server by default will use what's set or if you want the same for everyone, just put override settings and set it in admin tools/ terminal services configuration
here is a shorter but to the point version of what I typed before (sorry short on time)
Active Directory accounts have a tab to set it per account.
The server by default will use what's set or if you want the same for everyone, just put override settings and set it in admin tools/ terminal services configuration
I have also included an image since the first one got whacked by stupid software that rebooted my computer
http://techtips.deadnight.com/ee/Q_21805527.htm
http://techtips.deadnight.com/ee/Q_21805527.htm
try playing with this policy
computer components - admin templates - windows components - terminal services \ restrict terminal services users to a single remote session
computer components - admin templates - windows components - terminal services - sessions \ set time limit for disconnected sessions
Cheers!