TS Licensing with Win98 clients problem

[Wayne]

We have a Win2k terminal server, with 15 Windows 98
clients connecting from remote sites over VPN and dial-
up. Only 3 or 4 are ever able to connect and log in.
When the others try to connect, they get an error on their
workstations, and on the server, there is a 1004 "The
terminal server cannot issue a client license." If a new
Win98 client connects the first time, it will allow the
connection. But when it tries to connect the second time,
it gets the error and will not allow a connection. We
have 25 TSCALs installed on this server (the TS and LS run
on the same server), with 19 available. Has anyone else
run into this?

Thanks,

Wayne

 

[Cláudio Rodrigues]

This happened a lot when using DSL to connect. There is a fix on the KB for
that, post SP4 If I am not wrong.
As a workaround, try reducing the MTU size on the TS itself.

--
Cláudio Rodrigues

Microsoft MVP
Windows Technologies - Terminal Services
http://www.terminal-services.net

 

[Wayne]

Do you happen to have the KB item number, or maybe a link
to it?

Wayne

 

[David Brandt [MSFT]]

The link below goes to what I think he was referring too, and give it a look
see, but the error msg is a bit different;
274805 Error Message: Terminal Server Has Ended the Connection
http://support.microsoft.com/?id=274805

Are you also using Citrix or is this just rdp?
Is this a 2k dc, or is it running in an NT4 domain?
What service pack does the 2k ts have installed?
When you say that not more than 4 or 5 clients can connect, is that at the
same time (ie, once 5 connect nobody else can even though they could
earlier) or is it that just 5 clients out of your total number are able to
successfully connect.
Were the 6 cals it did issue recently or early on after it was installed.

Are you seeing Licenses, either temp or regular, being issued in the
licensing mgr when clients try to connect?
These will help determine if ts is still finding the LS even on itself, if
licensing is working properly or at all, if we're limited via rdp connection
limits set in ts, etc.
What error msg do the clients see when they fail (ts has ended the
connection, etc)?

probably not the problem, but check the client perms in;
Edit the permissions in the registry on the Terminal Server Client computer:

a. Start Registry Editor (Regedt32.exe).

b. Locate the following key in the registry:


HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\LICENSE00x

c. Click Security, and then click Permissions.

d. Set the permission for Everyone to Full, and then click OK.

e. Quit Registry Editor.


--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
Do you happen to have the KB item number, or maybe a link
to it?

Wayne

 

[Guest]

1. Are you also using Citrix or is this just rdp?
- In addition to the Win2k TS, we have a WinNT server
running Citrix.

2. Is this a 2k dc, or is it running in an NT4 domain?
- We are running on an NT domain. The Win2k TS also has
the TS licensing server on it.

3. What service pack does the 2k ts have installed?
- SP4.

4. When you say that not more than 4 or 5 clients can
connect, is that at the same time (ie, once 5 connect
nobody else can even though they could earlier) or is it
that just 5 clients out of your total number are able to
successfully connect?
- The same four or five clients can connect. Other client
can make an initial connection the first time they try,
and it looks like the server issues a temp license, but
when they try to connect again, it will not allow a
connection.

5. Were the 6 cals it did issue recently or early on after
it was installed?
- Early on, shortly after the servere was put in
production.

6. Are you seeing Licenses, either temp or regular, being
issued in the licensing mgr when clients try to connect?
These will help determine if ts is still finding the LS
even on itself, if licensing is working properly or at
all, if we're limited via rdp connection limits set in ts,
etc.
- I saw a lot of temp licenses being issued; the stations
that can connect have regular licenses issued.

7. What error msg do the clients see when they fail (ts
has ended the connection, etc)?
- Something similar to that, yes.

Any ideas?

Wayne