remote computer disconnected the session because of an error in th

[GillH]

We moved our Windows 2000 TS machine from an NT4.0 domain to an active
directory domain with a mix of 2000 and 2003 domain controllers. The domain
functional level is Windows 2000 native. We realized after the fact that the
licensing server could not longer run on the Windows 2000 TS server and moved
it to a Windows 2003 domain controller in the same site with the help of the
MS clearing house.

XP clients that previously connected to the terminal server still work fine.
New clients get the message 'remote computer disconnected the session because
of an error in the licensing protocol'. We tried deleting the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing registry key on the new XP
machines but continue to get the same error.

 

[Drew Hammond [MSFT]]

Re: remote computer disconnected the session because of an error in th

Hi Gill,

Check the suggestions on this TechNet site:
http://technet2.microsoft.com/Windo...4edb-43fd-8767-3d9858897e2c1033.mspx?mfr=true

Did you reboot the XP Client after deleting the registry key? I don' think
it's strictly required to rebuild that reg key, but is suggested per the
above site.

You might also check that your new client can ping the license server by IP,
FQDN & NetBios name, if those fail, DNS configuration may need to be
adjusted.

--
Drew Hammond - Terminal Services Developer in Test
This posting is provided "AS IS" with no warranties, and confers no rights
TS Team blog: http://blogs.msdn.com/ts

"GillH" <gilliii@discussions.microsoft.com> wrote in message
news:63D531BA-5D0D-4887-B4A9-5D1FCCFBC556@microsoft.com...
> We moved our Windows 2000 TS machine from an NT4.0 domain to an active
> directory domain with a mix of 2000 and 2003 domain controllers. The
> domain
> functional level is Windows 2000 native. We realized after the fact that
> the
> licensing server could not longer run on the Windows 2000 TS server and
> moved
> it to a Windows 2003 domain controller in the same site with the help of
> the
> MS clearing house.
>
> XP clients that previously connected to the terminal server still work
> fine.
> New clients get the message 'remote computer disconnected the session
> because
> of an error in the licensing protocol'. We tried deleting the
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing registry key on the new
> XP
> machines but continue to get the same error.

 

[GillH]

Re: remote computer disconnected the session because of an error i

Re: remote computer disconnected the session because of an error i

Drew,

Thanks for the reply.

We've already went through the articles you reference on the Technet site
before ever posting here and nothing has helped. We did reboot the XP
machine(s) after deleting the registry key. We've tried more than one XP
system and tried deleting the license key on each more that once.

All clients can ping the servers by IP, hostname and netbois names and the
servers with each other. All clients can browse resources on both server by
running '\\servername'.

I'm wondering if there is something 'embedded' in the Windows 2000 TS that's
causing it to look only at itself since it was originally the TS License
server and that abruptly changed when we joined it to the new domain.

"Drew Hammond [MSFT]" wrote:

> Hi Gill,
>
> Check the suggestions on this TechNet site:
> http://technet2.microsoft.com/Windo...4edb-43fd-8767-3d9858897e2c1033.mspx?mfr=true
>
> Did you reboot the XP Client after deleting the registry key? I don' think
> it's strictly required to rebuild that reg key, but is suggested per the
> above site.
>
> You might also check that your new client can ping the license server by IP,
> FQDN & NetBios name, if those fail, DNS configuration may need to be
> adjusted.
>
> --
> Drew Hammond - Terminal Services Developer in Test
> This posting is provided "AS IS" with no warranties, and confers no rights
> TS Team blog: http://blogs.msdn.com/ts
>
> "GillH" <gilliii@discussions.microsoft.com> wrote in message
> news:63D531BA-5D0D-4887-B4A9-5D1FCCFBC556@microsoft.com...
> > We moved our Windows 2000 TS machine from an NT4.0 domain to an active
> > directory domain with a mix of 2000 and 2003 domain controllers. The
> > domain
> > functional level is Windows 2000 native. We realized after the fact that
> > the
> > licensing server could not longer run on the Windows 2000 TS server and
> > moved
> > it to a Windows 2003 domain controller in the same site with the help of
> > the
> > MS clearing house.
> >
> > XP clients that previously connected to the terminal server still work
> > fine.
> > New clients get the message 'remote computer disconnected the session
> > because
> > of an error in the licensing protocol'. We tried deleting the
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing registry key on the new
> > XP
> > machines but continue to get the same error.
>
>

 

[Cláudio Rodrigues [MVP]]

Re: remote computer disconnected the session because of an errori

Re: remote computer disconnected the session because of an errori

GillH wrote:
> Drew,
>
> Thanks for the reply.
>
> We've already went through the articles you reference on the Technet site
> before ever posting here and nothing has helped. We did reboot the XP
> machine(s) after deleting the registry key. We've tried more than one XP
> system and tried deleting the license key on each more that once.
>
> All clients can ping the servers by IP, hostname and netbois names and the
> servers with each other. All clients can browse resources on both server by
> running '\\servername'.
>
> I'm wondering if there is something 'embedded' in the Windows 2000 TS that's
> causing it to look only at itself since it was originally the TS License
> server and that abruptly changed when we joined it to the new domain.
>
> "Drew Hammond [MSFT]" wrote:
>
>> Hi Gill,
>>
>> Check the suggestions on this TechNet site:
>> http://technet2.microsoft.com/Windo...4edb-43fd-8767-3d9858897e2c1033.mspx?mfr=true
>>
>> Did you reboot the XP Client after deleting the registry key? I don' think
>> it's strictly required to rebuild that reg key, but is suggested per the
>> above site.
>>
>> You might also check that your new client can ping the license server by IP,
>> FQDN & NetBios name, if those fail, DNS configuration may need to be
>> adjusted.
>>
>> --
>> Drew Hammond - Terminal Services Developer in Test
>> This posting is provided "AS IS" with no warranties, and confers no rights
>> TS Team blog: http://blogs.msdn.com/ts
>>
>> "GillH" <gilliii@discussions.microsoft.com> wrote in message
>> news:63D531BA-5D0D-4887-B4A9-5D1FCCFBC556@microsoft.com...
>>> We moved our Windows 2000 TS machine from an NT4.0 domain to an active
>>> directory domain with a mix of 2000 and 2003 domain controllers. The
>>> domain
>>> functional level is Windows 2000 native. We realized after the fact that
>>> the
>>> licensing server could not longer run on the Windows 2000 TS server and
>>> moved
>>> it to a Windows 2003 domain controller in the same site with the help of
>>> the
>>> MS clearing house.
>>>
>>> XP clients that previously connected to the terminal server still work
>>> fine.
>>> New clients get the message 'remote computer disconnected the session
>>> because
>>> of an error in the licensing protocol'. We tried deleting the
>>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing registry key on the new
>>> XP
>>> machines but continue to get the same error.
>>
Try enforcing on the TS registry the license server IP address.
Also, the licensing server CAN actually run on the TS even on 2000. All
you need is a --nodc switch in the service properties.
Look for it on Google.

--
Cláudio Rodrigues
CEO, TSFactory Inc.

Microsoft MVP
Windows Server - Terminal Services
http://www.tsfactory.com