Windows Forum

Ask something
Discussion Locked

Terminal Services Licensing

0 helpful
4 replies

by jkandris

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Okay here is my problem. I have several different remote users. The network is this Win 2k Sp4 full AD all that stuff. Citrix Metaframe Xp FR3. Some of the clients cannot access from outside while others can. I proved this weirdness in this way. My home network. Wireless broadband etc etc. My desktop win98 cannot connect back to the internal network through Nfuse or P/N but my laptop Win Xp Pro can connect through NFuse and program neighborhood. The error that is listed the event log is this The terminal server cannot issue a client license. Event ID 1004. I saw an earlier entry in the log that was this. The Terminal Services Licensing server VACOMETA has no license pack registered for product 'Windows 2000 Terminal Services Client Access License'. Use Terminal Services Licensing administrative tool to register the licenses pack. Event ID 22. I have done all that stuff previously. ANy IDeas.

4 replies

by julie.schneider

Found this on eventid.net in response to eventid22

Numerous attempts were made to resolve the problem (clients could not connect, mostly Win2K but also a few WinXP). When connecting with Citrix, the connection would start but would terminate immediately without an error message, except for event id 1004 which appeared on the terminal/citrix server. A call to Microsoft and numerous attempts to fix this on the server side yielded nothing. The only thing that resolved the issue was to delete the "HKLM\Software\Microsoft\MSLicensing" subkeys "HardwareID" and "Store" (which causes the client to re-register and basically eat up another CAL) on every client.

by jkandris

The document that I found said nothing about deleting that other key. That solved. THANKS A TON!!!!!!!!!!!!

This discussion is closed to new replies.