HI Guys,
I am experiencing the issue described in the (Article ID: 834651) and wanted to seek clarification
In the situation we are seeing this, only one external client is being affected. The site is a Very busy 24hr Dr Surgery, and the W2K3 terminal server is used internally plus by the Doctors and Surgeons from the Hospital and from home.
- Only one Dr at this stage has been identified as being affected from his home work-group.
- His work-group at his home office has Win7, Win8 and Vista machines and is connecting via his shared ADSL service.
- All machines on his work-group are being rejected with the same reason an event logged in the W2K3 server System event log has event 1028 "The terminal server client BOB-PC has been disconnected because its license could not be renewed. The license server ABCDEF was contacted to get Windows Server 2003 - Terminal Server Per Device CAL Token. license for this client."
- While he is trying to connect, about 30 odd staff are connected internaly (on the LAN) without any issue
- I tested a connection via RDP from my office and it connects ok, and gets to the point of asking for credentials. In the Dr's case it doesn't get to the prompt for uname and pwd.
If I make the change to the registry value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\Licensing Core\PolicyAcOn, changing it from its current value 2 to 4, is this a seamless change, or is there a likliehood of further issues.
I have only recently taken over support of the practice, and documentation of the system is non existent