Re: problem accessing TS

I'm glad that your problem is solved, but it is a bit scary that
the EventLog didn't record any warnings.
Thanks for reporting back here!

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

"guloga" <guloga@xxxxxxxx> wrote on 17 maj 2005 in
microsoft.public.windows.terminal_services:

> I have discovered that this a a licensing problem. The strange
> is that until now, there has been no message at EventLog. I have
> activated the licenses and now everything is working fine again.
>
> Million thanks to all for your help.
>
> Guloga
>
> "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> in message
> news:Xns9658E8746DC9veranoesthemutforsse@xxxxxxxxxxxxxxxx
>> If your DC runs W2K, and the TS Licensing Server runs on the
>> DC, then that's your problem (which is consistent with that it
>> worked since January).
>> Your 2003 TS cannot connect to a W2K Licensing Server, because
>> a W2K LS cannot handle 2003 licenses.
>> So since January the 2003 TS has been working in the "grace
>> period" (since it was unable to find a TS Licensing Server),
>> and now that the 120-days grace period has ended, you cannot
>> connect. Only thing that's weird is that this should be
>> recorded in the EventLog on the Terminal Server.
>>
>> You will need to install and activate the TS Licensing Service
>> on the 2003 server, and install 2003 TS CALs on it.
>>
>> Windows Server 2003 Pricing and Licensing FAQ
>> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pr
>> icl icfaq.mspx
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "guloga" <guloga@xxxxxxxx> wrote on 16 maj 2005 in
>> microsoft.public.windows.terminal_services:
>>
>>> Hi Vera,
>>>
>>> responding to your questions, i can tell you that the 2003 TS
>>> es a memeber server of the domain, and the users are members
>>> of the local Remote Desktop Users gruop.
>>>
>>> I see no errors on EventLog about TermServ, just some old ones
>>> about printers and some other applications. It has been
>>> working ok since January. The licensing server is at the DC
>>> server, the licences are intall Per Device.
>>>
>>> It seems like I don't know why, all the user (even the admin
>>> user) has lost
>>> the permissions.
>>>
>>> Thanks a lot for your help.
>>>
>>> Guloga...
>>> "Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>> wrote in message
>>> news:Xns96589D7401027veranoesthemutforsse@xxxxxxxxxxxxxxxx
>>>> The 2003 terminal Server is a member server in the domain, I
>>>> assume? And your users are members of the local Remote
>>>> Desktop Users group on the Terminal Server?
>>>>
>>>> Have you checked the EventLog on the Terminal Server?
>>>> How long has this been working OK?
>>>> And just to cover all the possibilities, does the 2003 TS
>>>> also run the TS Licensing Service? Did you install Per User
>>>> or Per Device TS CALs on it? And is it issueing TS CALs?
>>>>
>>>> --
>>>> Vera Noest
>>>> MCSE,CCEA, Microsoft MVP - Terminal Server
>>>> http://hem.fyristorg.com/vera/IT
>>>> *----------- Please reply in newsgroup -------------*
>>>>
>>>> "guloga" <guloga@xxxxxxxx> wrote on 16 maj 2005:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I am experiencing some strange problems with my Terminal
>>>>> Server. Everything was running ok, but this morning, when
>>>>> users went to logon, they get a dialog box saying "To logon
>>>>> on to this remote computer, you must have Terminal Server
>>>>> User Access permissions on this computer. By default,
>>>>> members of the Remote Desktop Users group have these
>>>>> permissions. If you are not a member of the Remote Desktop
>>>>> User groupor another group that has these permissions, or if
>>>>> the Remote Desktop User group does not have these
>>>>> permissions, you must be granted these permissions
>>>>> manually".
>>>>>
>>>>> I am using a Windows Server 2003 for TS, and a Windows 2000
>>>>> Server as the DC in the Active Directory. I have checked the
>>>>> Permissions for Remote Desktop User group and everything
>>>>> seems to be right. Please, can any body help me?
>>>>>
>>>>> Thanks a lot for your help.
>>>>>
>>>>> Guloga
.

Relevant Pages

  • Re: Licensing
    ... Vera Noest wrote: ... If you're not using the LS on the 2003 server anymore and you have moved your licenses, you should uninstall the TS Licensing Sevices from it. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: problem accessing TS
    ... I have discovered that this a a licensing problem. ... there has been no message at EventLog. ... > If your DC runs W2K, and the TS Licensing Server runs on the DC, ... > MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to find TS licensing server
    ... Vera Noest ... MCSE, CCEA, Microsoft MVP - Terminal Server ... this AM I hard-coded the TSLS ... > TSLS when going into TS Licensing. ...
    (microsoft.public.windows.terminal_services)
  • Re: Canīt connect a WVista Home to Terminal Server.
    ... Server logs a record saying that it can't issue a license. ... Are there any errors in the EventLog on the TS? ... TS, i think is about licensing, i have deleted the MS Licencing ... Carpets in Registry as in WXP, but this WVista do not rebuild ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server Licensing Server Keeps being disabled
    ... Vera Noest ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Got a problem with our windows 2000 terminal licensing ... Licences are also not issued which seems to cause problems ...
    (microsoft.public.windows.terminal_services)