1 of 10 clients cannot issue a license

[Guest]

I'm having problems with a terminal service client, which cannot connect to a terminal server. The server log displays an event ID 1004 (nothing registered on the knowledge base), with the description "The terminal server cannot issue a client license".
Even though all the other clients can connect to the server, this particular client cannot.
The connection to the server is established via a VPN connection, and the client is able to PING and browse the server's shares.

 

[Vera Noest [MVP]]

Don't know what search terms you used, but I get pages of KB articles
searching for "event 1004 client license".

If you are sure that you have enough TS CALs available on your TS
Licensing Server, then the problem could be caused by a "black hole
router", which drops packets above a certain size. The new license
can be too big to be transferred to your client. The Microsofts
Terminal Services FAQ at
http://www.microsoft.com/windowsserver2003/community/centers/terminal
/terminal_faq.asp

has 2 Q&As about this under "Connectivity". You might have to change
the MTU size.

 

[Matthew Harris [MVP]]

Can the usr telnet to port 3389 of the terminal server
once they are in the VPN (telnet <ip_address> 3389)?

Have you tried deleting the MSLicensing registry key from
the client's registry?

-M

-----Original Message-----
I'm having problems with a terminal service client, which

cannot connect to a terminal server. The server log
displays an event ID 1004 (nothing registered on the
knowledge base), with the description "The terminal server
cannot issue a client license".

Even though all the other clients can connect to the

server, this particular client cannot.

The connection to the server is established via a VPN

connection, and the client is able to PING and browse the
server's shares.