Lincensing

[Guest]

Situation
- Windows 2000 server version 5.00.2195 SVPK4 running TS
- Installed per sea
- TS lincensing is active with 5 issues "Windows 2000 server - Terminal services CAL Token (Per-device)
- I see in the "Teminal services licessing" interface only 2 entries
Existing Windows 2000 License Built-in Tot=Unlimited avail= unlimited Issued=
Win 2000 server - Terminal Services CAL token (per device) Open Tot=5 avail=3 Issued=
- I see 5 sessions open in "Terminal services manager" every one are WBT with WIN CE

Problem
- I try to connect with my PC (WinXP pro) and I got "Event ID 1004" "The terminal server cannot issue a client license
- My workmate has his PC (WinXP pro) has no problem to open a session

Question
Why most of the PC with winXP PRO can't connect to the server? (Only one can
Why I don't see the entry "Temporary licence" in the licence interface
Why I have 5 appliances sessions opens and I see only 2 tokens issues
I bought TCAL for win 2003 server because TCAL for 2000 is no avalaible so far. Maybe it's the problem

Thanks

 

[Vera Noest [MVP]]

Have you checked if the TS can locate the LS? Search for EventID
1010 "cannot locate licensing server". If that's the problem, try
to hardcode the address of the LS into the registry of the TS
(even when they are running on the same server):

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

Have you tried to delete the license from your XP Pro workstation?
187614 - Removing Terminal Server Licenses from an RDP Client
http://support.microsoft.com/?kbid=187614

 

[Vera Noest [MVP]]

No, you cannot install the 2003 Licensing Service on a W2K server.
And your XP Pro client should get one of the "Existing Windows 2000
Licenses" anyway, not one of you purchased TS CALs.

Is your PC on the same LAN as the Terminal Server?

 

[Vera Noest [MVP]]

There might be a black hole router between your client and the TS,
which blocks packets above a certain size. This prevents the
transfer of the permanent TS CAL to the client (on first
connection, the client gets a temporary license, on second
connection, it gets a permanent license).

If this is the problem, you have to change the MTU size. Check the
Terminal Services FAQ, there are 2 items about this under
"Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/termi
nal/terminal_faq.asp

About the licenses themselves: you can install 2003 TS CALs on a
W2K LS, by using your downgrade rights. You will need to have them
activated as Windows 2000 CAL's during the install process.
But again: that's not the core of your problem, since your XP Pro
client should get one of the "Existing Windows 2000
Licenses" anyway, not one of your purchased 2003 TS CALs.

 

[Guest]

1-) My wan connection use a VPN-CISCO. From client site (T1 1.5 Mb/s) to server site (ADSL). The internet provider of ADSL services suggest to use MTU=1492. All customers with ADSL have MTU=1492. Do you suggest ne to change the MTU anyway for this customer

2-) Why one login in the client site can connect to the server from any PC. All others login can't connect from any

 

[Vera Noest [MVP]]

No, I suggest that you *test* which MTU size is appropriate for
this connection. Depending on the outcome of the test, you can
choose a fix or workaround:

314825 - How to Troubleshoot Black Hole Router Issues
http://support.microsoft.com/?kbid=314825

But if the problem is user-specific, then you should focus on the
differences between these user accounts. You need to have the
right to edit the local registry key that stores the license on
the client. Any differences there? Can you logon when you use an
account that has administrative rights on the local PC?

If the problem is client (PC) specific, then it can simply mean
that the PCs which are able to connect have received a valid
license in the past, and it is still valid. The PCs which can't
connect have no license, or an expired license.

 

[Vera Noest [MVP]]

OK, so the problem is client-specific, not user-specific.

And the first logon after deleting the local license works
(receiving a temporary license), but the second connection
generates Event 1004 (on second connection, the full TS CAL nust
be transferred to the client).
Assuming that all clients run the same OS, and that there is no
shortage of available TS CALs on the LS, this is consistent with a
black hole router problem.

How about your MTU test?

 

[Guest]

I made the test with ping -f -l {len

PC Y : ping {ip} -f -l 1272 O
ping {ip} -f -l 1273 Packet must defra

HOST (with connect error) HOST (Connect OK
PC Z ping {ip} -f -l 1370 OK 1402 O
ping {ip} -f -l 1371 request time out 1403 request time out
ping {ip} -f -l 1414 request time out 1414 request time ou
ping {ip} -f -l 1415 packet must defrag 1415 packet must defra

 

[Vera Noest [MVP]]

OK, have you lowered the MTU accordingly? Did that solve the problem?

 

[Guest]

I changed teh MTU for 1370+28=1398 and That's rights
Congragulation Vera

I'm just worry about the fact to change the value on the PC
Communicatation Slower?

 

[Vera Noest [MVP]]

I can't give you any guarantees here, but I don't believe that
communication will be significantly slower. By lowering the packet
size, you prevent defragmentation and/or dropped packets. Surely,
that's a enhancement of the communication
But it should be easy to try it out, and time some file transfer
rates before and after the change.

 

[Guest]

Thanks again Vera
File closed.