Hi all,

I have a Win 2000 box with SP3 applied. 20 TS CALs have been installed for my Win based terminals clients (WinCE.net).
Each has got a token. An expiration date appears for each client on my licence server (the same server). I've read somewhere that's it's correct. (the licences issued are NOT temp licences, but "per-device" licences.
BUT: when the espiration date arrives for a cient, that client can't connect for the whole day.
The next day, it's possible... and the expiration date is changed.

Any ideas? Should i reinstall the LS server ?

Thanks for having read the post, ... and to answer if you can help.

Yan

This is a known issue, which is fixed in SP4. Check this for a
workaround or hotfix:

813508 - Cannot Connect to a Terminal Server From a Windows-Based
Terminal
http://support.microsoft.com/?kbid=813508

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

=?Utf-8?B?WWFu?= <(E-Mail Removed)> wrote in
news:3D86805D-CB8D-4D26-A36D-(E-Mail Removed):

> Hi all,
>
> I have a Win 2000 box with SP3 applied. 20 TS CALs have been
> installed for my Win based terminals clients (WinCE.net). Each
> has got a token. An expiration date appears for each client on
> my licence server (the same server). I've read somewhere that's
> it's correct. (the licences issued are NOT temp licences, but
> "per-device" licences. BUT: when the espiration date arrives for
> a cient, that client can't connect for the whole day. The next
> day, it's possible... and the expiration date is changed.
>
> Any ideas? Should i reinstall the LS server ?
>
> Thanks for having read the post, ... and to answer if you can
> help.
>
> Yan