Link to home
Start Free TrialLog in
Avatar of NARRIOLA
NARRIOLA

asked on

Terminal Services gets automaticaly terminated

We currently have 2 users with Windows 98 that is trying to connect to Terminal Services but everytime they try it disconnects them automatically even before they get  to the login screen. Any ideas ?
Avatar of oBdA
oBdA

You need to give more information here.
Terminal Services running on NT4, W2k, W2k3?
Is that an NT4 domain or W2k(3) Active Directory?
Which version of the RDP client are you using on the Win98 boxes?
Is there anything in the event log of the Terminal Servers?
Can other clients logon to Terminal Services? If so, what OS are they running?
Do you have a license server up and running, is it activated, do you have the proper amount of licenses added?
Avatar of NARRIOLA

ASKER

Terminal Services running on W2k
W2k Active Directory?

Which version of the RDP client are you using on the Win98 boxes?
Version 5.1

Is there anything in the event log of the Terminal Servers?
The event log shows. "Terminal Sever cannot issue a Client License"

Can other clients logon to Terminal Services? If so, what OS are they running?
Only a random number of users cannot login.  So far 6 people have reported being rejected for connection.  All of them are using Windows 98.

Do you have a license server up and running, is it activated, do you have the proper amount of licenses added?
Yes
Maybe I should clarify the license server question, I wasn't clear at the first try: Do you have a *Terminal* *Services* license server installed, and if so, where?
If the Terminal Server can't issue a client license, it either can't find the Terminal Services license server, or you don't have the necessary licenses installed.
Unlike W2k/XP clients, you need TS CALs for Win9x clients accessing a W2k Terminal Server.
Yes we have a TS license Server installed in another site and TS machine is able to communicate to that server.  I am suspecting that the TS CALs is the problem.
If you can start the RDP client on a W2k or XP machine, but not on a Win9x machine, then it's a TS CAL problem.
But just in case:
Establishing Preferred Windows 2000 Terminal Services License Server
http://support.microsoft.com/?kbid=239107
I found out the solution.  The problem was with the HW ID on the workstation CAL.  I believe that the license being used is temporary.  By changing the HW ID code on the Workstation it then allowed me connect to the TS Server.  Thank you for your help anyway.  This case is now closed.
ASKER CERTIFIED SOLUTION
Avatar of modulo
modulo

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial