Win9x Terminal Service client cannot reconnect

[Psychoid]

Hi Everyone.
The environment is: W2K server w/sp2 and the SRP with Win9x terminal service clients

The problem:
One Win9x TS client can connect to TS, but then can't connect on any subsequent tries (the client times out and the event log on the server gives an ID1004 "terminal server cannot issue a client license&quot. The only way to get it to reconnect is to do a regedit and remove the license000 key. Once that's done, it will reconnect, but, again, can't on any subsequent tries.

The TS Licensing says that this client has a licensed connection, not just a temporary one.

The Win9x client is a freshly fdisk'd and installed machine.

Any ideas?
Thanks
Bill ------------
Certified in absolutely nothing

 

[TheMac28nearly]

Ive had a very similar problem only my clients are completely thin with a boot rom attached and we are using an app called thin manager.

We have 2 TS servers and it would connect fine to TS1 but got the error your talking about when trying to connect to TS2. Both servers have cals as its a failover environment. Coincedentally the HD on TS1 failed and we replaced it yesterday, the Licence server has not been activated but TS2 has now allocated a licence.

Any ideas on why this would happen when a new server appears on the network like this. Would like to know to help it avoid happening again

 

[GlenJohnson]

What are your TS manager settings? You have enough licenses? I assume your not running this in admin mode so only two connections can be made. Good luck. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com

"By attempting the impossible, the possible is achieved."
Henri Barbusse (1873-1935); French writer.

 

[Dmasch]

In Win2k Server running terminal server sessions from a machine other than W2k Pro like you are. You will need to purchase additional TS CALS. Win2k Server has Win2k pro Cals built in but when you use Win98 you need to purchase other cals. You have 90 days of temporary licenses which the Win98 can use but after that you have to buy other cals for non Win2k pro machines. Hope that helps.

 

[ShayneK]

The license certificate is actually stored on the workstation within the registry. so everytime you delete that registry setting or format and redo the computer you are telling the license manager to issue a new license. And obvously if you don't have any available licenses it won't give you one.

Actually I really need to write more but I have a meeting for the rest of the day, so in short:

- If you have installed Terminal Services License Manager and you have purchased and installed the correct amount of licenses, you will need to call Microsoft to release and reissue the licenses...I've had to do this before and it's really painless. I forget exactly where the phone number is but I think if you go into the licensing manager and choose to install more licenses by phone it will give you the number.

More info:

http://www.microsoft.com/windows2000/techinfo/howitworks/terminal/tslicensing.asp

Shayne

 

[Psychoid]

Everyone,
Just a little more info:

1. The TS runs in application mode.
2. This client has a 5 license pack. In TS Licensing, there are 4 licenses free and one has been assigned to this problem workstation.
3. The first time that the client connects to the TS, it receives its license (license000); however, it cannot connect on subsequent tries.
4. The client isn't using a temporary license; according the the terminal server, the client has a real one.

Hope that clarifies things
Bill ------------
Certified in absolutely nothing

 

[TheMac28nearly]

Just to add a little bit more to my issue

TS2 server had 15 licenses, 10 of which were available for the client

I am running in App Server mode

The TS2 server actually reported Event ID 1004 - 'Cannot issue a Client Licence' when this client tried to connect.

 

[Psychoid]

Just in case anybody is wondering, I found the problem:
AOL 7

This user was actually connecting through AOL7 to our vpn, then using the TS client to connect to the terminal server. The workstation would connect once, but never again after that.

So, on a hunch, I uninstalled AOL7, installed AOL6, and everything worked fine.

As further proof, I installed AOL7 again and the problem re-occurred.

So, if you have a remote user who needs VPN/Terminal Service access to your network, make sure that they don't use AOL7.

Bill ------------
Certified in absolutely nothing