Re: licensing protocol question-I'm at the end of my rope

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Thomas Scheff (lifestar664_at_hotmail.com)
Date: 04/12/04


Date: Mon, 12 Apr 2004 09:06:11 -0400


On Fri, 09 Apr 2004 11:06:40 -0700, "Vera Noest [MVP]"
<vera.noest@remove-this.hem.utfors.se> wrote:

>OK, that means that you are receiving a temporary license on your
>first connection, but the issueing of the permanent license (which
>always happens on the second connection) fails.
>
>To find out the reason for this, can you anser these questions:
>* Do you get an EventID 1010 in the system log on the TS?
>* In TS Licensing Manager, can you verify that the other clients
>(that can connect) have received a permanent TS CAL?
>* Are you running XP Pro or XP Home Edition on the client that
>can't connect?
>* If XP Home, have you verified that there is a free TS CAL
>available in TS Licensing Manager?
>* If XP Pro (which should get an "Existing Windows 2000 TS CAL"),
>is this client located on the same LAN as the other clients and
>the Licensing Server, or are you connecting through a WAN?
>* If XP Pro, have you tried the solution from this KB article:
>
>323597 - Windows XP Clients Cannot Connect to a Windows 2000
>Terminal Services Server
>http://support.microsoft.com/?kbid=323597

1. I do not see event ID 1010, only 1004
I looked in the TS Licensing (start-programs-admin tools-licensing) on
the box I am trying to connect to and I see the following under
products view
per seat purchased--0
per seat allocated--186
per server allocated--3099
per server reached---123

On the box I can connect to I see this,
per seat purchased--0
per seat allocated--55
per server allocated--55
per server reached---24.
I'm running XP Pro, it's on a LAN, but the devices are not on the LAN,
but the WAN.

How do I verify there is a free TS CAL?

I'll check that articke next.
Thanks

>
> --
>Vera Noest
>MCSE, CCEA, Microsoft MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
>Thomas Scheff <lifestar664@hotmail.com> wrote in
>news:vl7d70li5umklcc62esp94q94gp2299sgj@4ax.com:
>
>> What's happeing is I can't delete the key from the registry, but
>> if I delete the MSLisencing, I guess it's a file, then I can
>> connect. This only solves the problem temporarily, when I close
>> out, the key is back, and I have to delete the file again.
>>
>>
>> On Thu, 08 Apr 2004 11:15:24 -0700, "Vera Noest [MVP]"
>> <vera.noest@remove-this.hem.utfors.se> wrote:
>>
>>>Glad that your problem is solved, Thomas!
>>>I wouldn't recommend to anyone to "delete the registry, the
>>>entire thing" to solve problems, though! I'm not sure what
>>>exactly you deleted, but deleting more than the specific keys
>>>could render your machine unbootable.
>>>
>>> --
>>>Vera Noest
>>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>>http://hem.fyristorg.com/vera/IT
>>> --- please respond in newsgroup, NOT by private email ---
>>>
>>>Thomas Scheff <lifestar664@hotmail.com> wrote in
>>>news:05ma70php0hq2ff2dkqp7jprrflqjv3b2g@4ax.com:
>>>
>>>> Vera, I can't thank you enough. I deleted the registry, the
>>>> entire thing. I tried deleting the key, but couldn't, but when
>>>> I deleted the whole thing it worked.
>>>>
>>>> Thanks again. I'll be sure to give this information to anyone
>>>> else if I see them asking. Share the wealth I always say.
>>>> Thomas
>>>>
>>>>
>>>> On Wed, 07 Apr 2004 14:20:06 -0700, "Vera Noest [MVP]"
>>>> <vera.noest@remove-this.hem.utfors.se> wrote:
>>>>
>>>>>In the system log, I was wondering if you see an EventID 1010
>>>>>("cannot locate licensing server") there.
>>>>>
>>>>>I would check the TS Licensing Manager, it's possible that the
>>>>>other users are stil running on temporary licenses, and that
>>>>>you are simply the first one with an expired temporary
>>>>>license. You are running XP Pro, aren't you, not XP Home
>>>>>Edition? If you find in LS Manager that all other workstation
>>>>>have received a permanent license, then your problem seems to
>>>>>be associated with only your workstation. If that is the case,
>>>>>I would delete the license from your workstation, thereby
>>>>>forcing it to grab a new one.
>>>>>
>>>>>187614 - Removing Terminal Server Licenses from an RDP Client
>>>>>http://support.microsoft.com/?kbid=187614
>>>>>
>>>>>Check this article as well. Although the error message
>>>>>mentioned is slightly different, it has been reported to fix
>>>>>this type of problem.
>>>>>323597 - Windows XP Clients Cannot Connect to a Windows 2000
>>>>>Terminal Services Server
>>>>>http://support.microsoft.com/?kbid=323597
>>>>>
>>>>> --
>>>>>Vera Noest
>>>>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>http://hem.fyristorg.com/vera/IT
>>>>> --- please respond in newsgroup, NOT by private email ---
>>>>>
>>>>>Thomas Scheff <lifestar664@hotmail.com> wrote in
>>>>>news:42p870tmpgnl1pj0bgrhslt8bh0oshtum4@4ax.com:
>>>>>
>>>>>> It's WIN 2000
>>>>>> We have TS Licensing installed and activated. The other
>>>>>> admins and users can connect to this box, for some reaon I
>>>>>> can't. What do I look for in the event log, the application
>>>>>> log, system log or secirity log?
>>>>>>
>>>>>> On Wed, 07 Apr 2004 12:56:21 -0700, "Vera Noest [MVP]"
>>>>>> <vera.noest@remove-this.hem.utfors.se> wrote:
>>>>>>
>>>>>>>What OS is the Terminal Server running? W2K or 2003?
>>>>>>>Do you have a TS Licensing Server installed and activated?
>>>>>>>If not, that's the cause of the problem.
>>>>>>>If yes, have you verified that the TS can locate the LS?
>>>>>>>If yes, have you checked the status of your TS CALs in the
>>>>>>>TS Licensing Manager?
>>>>>>>Which EventIDs do you see on the TS?
>>>>>>>If the TS runs 2003, did you purchase and install TS CALs on
>>>>>>>the LS?
>>>>>>>
>>>>>>>Windows 2000 Terminal Services Licensing FAQ
>>>>>>>
>>>>>
>>>
>http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsfa
>>>>>>>q .asp
>>>>>>>
>>>>>>>Windows Server 2003 Pricing and Licensing FAQ
>>>>>>>
>>>>>
>>>
>http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pri
>>>>>>>c licfaq.mspx
>>>>>>>
>>>>>>> --
>>>>>>>Vera Noest
>>>>>>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>>http://hem.fyristorg.com/vera/IT
>>>>>>> --- please respond in newsgroup, NOT by private email ---
>>>>>>>
>>>>>>>Thomas Scheff <lifestar664@hotmail.com> wrote in
>>>>>>>news:9bk870lm1sjogvvt9e5rrqkqkrhgsb88hl@4ax.com:
>>>>>>>
>>>>>>>> I'm running remote desktop on Windows XP which ran fine
>>>>>>>> for awhile. Now I get this error.
>>>>>>>> "The remote computer disconnected the session because of
>>>>>>>> an error in the licensing protocol. Please try connecting
>>>>>>>> to the remote computer again or contact your server
>>>>>>>> administrator."
>>>>>>>>
>>>>>>>> The Microsoft knowledge base had this to say
>>>>>>>>
>>>>>>>> "Cause: The licensing protocol handles the communication
>>>>>>>> of licensing information between your computer and the
>>>>>>>> remote computer. If there is an error in the licensing
>>>>>>>> protocol, your computer cannot be connected to the remote
>>>>>>>> computer.
>>>>>>>>
>>>>>>>> Solution: Try connecting to the remote computer again. If
>>>>>>>> you continue to receive this error message, contact the
>>>>>>>> server administrator"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I'm the server admin, and I can't figure this out. Please
>>>>>>>> help! Where do I check to see if my license has expired?
>>>>>>>> It's such a strange problem because I can connect to other
>>>>>>>> servers in the domain, just not terminal servers.
>>>>>>>>
>>>>>>>> Please help



Relevant Pages

  • RE: "The remote computer has ended the connection" TS Application
    ... Have you verified that the licensing mode of the TS matches ... the type of licenses on the TS Licensing Server (Per Device / ... network tab of the rdp-tcp connection properties? ... documented after the installation of SP1 for Server2003 but I'm ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to use Terminal Server CALs purchased
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Configuration" and that double clicking on the "RDP" connection ... I'm not sure how many Windows User CALs are installed. ... If I go to the CP and click on "Licensing", ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to use Terminal Server CALs purchased
    ... Instead I de-activated the License server that was running on the terminal ... and that double clicking on the "RDP" connection would get you into ... I'm not sure how many Windows User CALs are installed. ... window from which I can chose my "Licensing Mode". ...
    (microsoft.public.windows.terminal_services)
  • Re: CALS do not work
    ... By installing Terminal Services, under Add Windows components. ... Did you reboot the server after installing TS? ... Check the number of allowed connections on the rdp-tcp connection - ... I then installed the Terminal Server Licensing on the 2003 ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Licensing over Citrix issuing problem
    ... the refuses everything else giving the no additional connection licences are ... Terminal Server Licensing on server SUKDDC01 has not been activated. ... Im sure its the TS Licensing as we have TWO Citrix Servers and BOTH dont ...
    (microsoft.public.windows.terminal_services)