RE: Win2000 TS refuses connection

Weird. I only know of one single situation where you would receive
a temporary 2003 TS CAL: if you connect to a 2003 Terminal Server.

There aren't any other 2003 servers in your domain, besides the
Licensing Server?

I really don't know what to advice you. You could delete the
locally stored license and then connect again and monitor what
happens in the Licensing Manager, to see if it happens again or if
it was a temporary problem.
But that won't tell you the underlying cause of the problem, and
obviously, you have to find that.

Is your 2003 LS running SP1? If not, you can also try this hotfix
or workaround, to enable the client to get a W2K TS CAL, but it
will still not fix the original problem:

837321 - You cannot connect to a Windows 2000 Terminal server if
your Windows Server 2003 Terminal Services license is expired
http://support.microsoft.com/?kbid=837321
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VGlt?= <Tim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 04 okt
2005 in microsoft.public.win2000.termserv.apps:

> Vera
> Verified that the Win2003 server is not in TS application mode.
> Most clients are W2kpro/XP. Below is a summary of the TS Lic
> server: Win2k TS CALs - 10 total, 1 available, 9 issued
> Existing Win2k server CALs - unltd total, unltd available, 64
> issued Temp Win2k CALs - 0 total, 0 available, 5 issued
> Temp Win2003 CALS - 0 total, 0 available, 9 issued
>
> The TempWin2003 are the ones that I would like to remove as all
> clients should be getting Win2k CALs.
>
> Tim
>
> "Vera Noest [MVP]" wrote:
>
>> Do you have free Windows 2000 TS CALs available on the TS
>> Licensing Server? Or are you running W2K Pro or XP Pro on the
>> client (those clients should receive a free W2K TS CAL from the
>> built-in pool)?
>>
>> Have you double-checked that none of your 2003 servers has
>> Terminal Services installed (implying Application Server mode)?
>> That's the most common mistake when people have experience with
>> W2K TS in Remote Admin mode and switch to 2003. If you only
>> want Remote Administration on 2003, you should *not* install TS
>> at all, just enable Remote Desktop for Administration, in
>> Control Panel - System - Remote.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?VGlt?= <Tim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 04
>> okt 2005 in microsoft.public.win2000.termserv.apps:
>>
>> > thanks for the reply. What we're trying to stop from
>> > happening is a temporary license given for 2003, which we're
>> > not running in application mode. Most of the time the license
>> > server provides a 2000 license which is correct.
>> >
>> > "Elisabet Soler" wrote:
>> >
>> >> The first time a user logon into a Terminal Server session,
>> >> server where the user logon search a License server for
>> >> terminal server. This give a temporary license to the server
>> >> for the user. Each time user logon into a Terminal Server
>> >> session, server try to find a Terminal Server CAL (or
>> >> permanet license). If it cannot find, it continue using the
>> >> temporary license until expire.
>> >>
>> >> You can delete this temporary license from the registry of
>> >> user's computer.
>> >> HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing
>> >>
>> >> Have you seen the event viewer? There are any error?
>> >>
>> >>
>> >>
>> >> "Tim" wrote:
>> >>
>> >> > Yes, activated for 14 months.
>> >> >
>> >> > "Elisabet Soler" wrote:
>> >> >
>> >> > > The Licence Server for Terminal server is activated?
>> >> > >
>> >> > > "Tim" wrote:
>> >> > >
>> >> > > > We have a Win2000 TS with a Win2003 TS License server
>> >> > > > (per device). Until recently, this was working fine.
>> >> > > > Now, the TS is refusing some client access because the
>> >> > > > license server has created a temporary license for
>> >> > > > 2003 server, and these client's licenses have expired.
>> >> > > > How do I remove the temporary 2003 server license as I
>> >> > > > don't have a 2003 TS established, and allow these
>> >> > > > clients to re-register with the Win2000 server?
.

Relevant Pages

  • RE: local computer client access license error
    ... the Terminal Server Licensing server only has Per User CALS. ... Windows Server 2003 does not manage User CALs. ... even though there is a User CAL in the license server database, ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Changing TS Licensing Mode
    ... 822134 - The Function of Terminal Server CALs in Windows Server ... MCSE, CCEA, Microsoft MVP - Terminal Server ... One question I do have is that on the License ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Confused about CALs
    ... You mention that the 5 CALs that come with the server do not ... Terminal Services client connection. ... License Server must be activated within 120 days of using the ...
    (microsoft.public.windows.terminal_services)
Loading