XP clients cannot connect to 2000 TS with 2003 license server

[Guest Jim]

Hi,

I have a Windows 2000 terminal server that is part of a domain where the

TS license server is a Windows 2003 server. Windows XP clients are being

refused connections to the 2000 server because of "an error in the

licensing protocol". I have made the registry entry for the license

server on the Windows 2000 server but error 1004 still appears in the

event log. The XP clients should still be able to connect to the 2000

server without a purchased CAL should they not?

TIA

[Guest Vera Noest [MVP]]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

Yes, they should.

Have you tried if they can connect if you delete the locally stored

license from the clients registry?

Try connecting twice and check in the TS Licensing Manager what

happens; on the first connection, clients receive a temporary

license, on the second connection, they should receive a permanent

license from the free pool of "Existing Windows 2000 Per Device TS

CALs".

 

http://technet2.microsoft.com/WindowsServer/en/library/159e6ff8-4edb-

43fd-8767-3d9858897e2c1033.mspx#BKMK_8

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Jim <nospam@any.time> wrote on 01 okt 2007 in

microsoft.public.windows.terminal_services:

> Hi,

> I have a Windows 2000 terminal server that is part of a domain

> where the TS license server is a Windows 2003 server. Windows XP

> clients are being refused connections to the 2000 server because

> of "an error in the licensing protocol". I have made the

> registry entry for the license server on the Windows 2000 server

> but error 1004 still appears in the event log. The XP clients

> should still be able to connect to the 2000 server without a

> purchased CAL should they not? TIA

[Guest TP]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

Hi,

 

XP Pro clients should receive a free TS CAL from the

built-in pool when connecting to a 2000 TS. XP Home

clients will *not*.

 

When you open up TS Licensing (licmgr.exe) and connect

to your 2003 TS Licensing server, what do you see?

 

- Is the server activated?

- Have any temporary licenses been issued? If so, from

what pool (post the precise Product name)?

- Have any permanent licenses been issued?

 

On your 2003 TS licensing server, what errors/warnings

appear in the System log, with a source of TermServLicensing?

 

On your 2000 TS, what licensing-related errors/warnings

appear in the System log with a source of TermService?

Please post the Description field as well, because this will

differ depending on the cause.

 

For example, look for Event IDs 1004, 1008, 1010, 1011, 1026

 

Thanks.

 

-TP

 

Jim wrote:

> Hi,

> I have a Windows 2000 terminal server that is part of a domain where

> the TS license server is a Windows 2003 server. Windows XP clients

> are being refused connections to the 2000 server because of "an error

> in the licensing protocol". I have made the registry entry for the

> license server on the Windows 2000 server but error 1004 still

> appears in the event log. The XP clients should still be able to

> connect to the 2000 server without a purchased CAL should they not?

> TIA

[Guest Jim]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

I have tried deleting the registry key. There is no change.

 

Vera Noest [MVP] wrote:

> Yes, they should.

> Have you tried if they can connect if you delete the locally stored

> license from the clients registry?

> Try connecting twice and check in the TS Licensing Manager what

> happens; on the first connection, clients receive a temporary

> license, on the second connection, they should receive a permanent

> license from the free pool of "Existing Windows 2000 Per Device TS

> CALs".

>

> http://technet2.microsoft.com/WindowsServer/en/library/159e6ff8-4edb-

> 43fd-8767-3d9858897e2c1033.mspx#BKMK_8

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> Jim <nospam@any.time> wrote on 01 okt 2007 in

> microsoft.public.windows.terminal_services:

>

>> Hi,

>> I have a Windows 2000 terminal server that is part of a domain

>> where the TS license server is a Windows 2003 server. Windows XP

>> clients are being refused connections to the 2000 server because

>> of "an error in the licensing protocol". I have made the

>> registry entry for the license server on the Windows 2000 server

>> but error 1004 still appears in the event log. The XP clients

>> should still be able to connect to the 2000 server without a

>> purchased CAL should they not? TIA

[Guest Jim]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

They are XP Pro clients. The licensing server is activated.

 

There are no existing Windows 2000 licenses listed on the licensing server.

 

There are two "Windows Server 2003 - Terminal Server Per Device CAL

Token" listings one for 5 and one for 25, all of which have been issued.

 

Temporary licenses have been issued as recently as last Thursday from

"Temporary Licenses for Windows 2003 Server - Terminal Server Per Device

CAL Token"

 

I don't think there are related events in the licensing server log, but

the Windows 2000 TS log has 1003, 1004, 1010 in that order when I try to

connect, so it appears the licensing server is not being located.

 

 

 

TP wrote:

> Hi,

>

> XP Pro clients should receive a free TS CAL from the built-in pool when

> connecting to a 2000 TS. XP Home clients will *not*.

> When you open up TS Licensing (licmgr.exe) and connect to your 2003 TS

> Licensing server, what do you see?

>

> - Is the server activated?

> - Have any temporary licenses been issued? If so, from what pool (post

> the precise Product name)?

> - Have any permanent licenses been issued?

>

> On your 2003 TS licensing server, what errors/warnings appear in the

> System log, with a source of TermServLicensing?

>

> On your 2000 TS, what licensing-related errors/warnings appear in the

> System log with a source of TermService? Please post the Description

> field as well, because this will differ depending on the cause.

>

> For example, look for Event IDs 1004, 1008, 1010, 1011, 1026

>

> Thanks.

>

> -TP

>

> Jim wrote:

>> Hi,

>> I have a Windows 2000 terminal server that is part of a domain where

>> the TS license server is a Windows 2003 server. Windows XP clients

>> are being refused connections to the 2000 server because of "an error

>> in the licensing protocol". I have made the registry entry for the

>> license server on the Windows 2000 server but error 1004 still

>> appears in the event log. The XP clients should still be able to

>> connect to the 2000 server without a purchased CAL should they not?

>> TIA

[Guest Vera Noest [MVP]]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

Well, at least we seem to have the cause of the problem:

> There are no existing Windows 2000 licenses listed on the

> licensing server.

But I have no idea why these built-in licenses aren't there. I've

no real good solution either, except that I would reinstall the LS.

 

273566 - How to rebuild Windows 2000 and 2003 Terminal Services

Licensing database

http://support.microsoft.com/?kbid=273566

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

Jim <nospam@any.time> wrote on 02 okt 2007:

> They are XP Pro clients. The licensing server is activated.

>

> There are no existing Windows 2000 licenses listed on the

> licensing server.

>

> There are two "Windows Server 2003 - Terminal Server Per Device

> CAL Token" listings one for 5 and one for 25, all of which have

> been issued.

>

> Temporary licenses have been issued as recently as last Thursday

> from "Temporary Licenses for Windows 2003 Server - Terminal

> Server Per Device CAL Token"

>

> I don't think there are related events in the licensing server

> log, but the Windows 2000 TS log has 1003, 1004, 1010 in that

> order when I try to connect, so it appears the licensing server

> is not being located.

>

>

>

> TP wrote:

>> Hi,

>>

>> XP Pro clients should receive a free TS CAL from the built-in

>> pool when connecting to a 2000 TS. XP Home clients will *not*.

>> When you open up TS Licensing (licmgr.exe) and connect to your

>> 2003 TS Licensing server, what do you see?

>>

>> - Is the server activated?

>> - Have any temporary licenses been issued? If so, from what

>> pool (post the precise Product name)?

>> - Have any permanent licenses been issued?

>>

>> On your 2003 TS licensing server, what errors/warnings appear

>> in the System log, with a source of TermServLicensing?

>>

>> On your 2000 TS, what licensing-related errors/warnings appear

>> in the System log with a source of TermService? Please post

>> the Description field as well, because this will differ

>> depending on the cause.

>>

>> For example, look for Event IDs 1004, 1008, 1010, 1011, 1026

>>

>> Thanks.

>>

>> -TP

>>

>> Jim wrote:

>>> Hi,

>>> I have a Windows 2000 terminal server that is part of a domain

>>> where the TS license server is a Windows 2003 server. Windows

>>> XP clients are being refused connections to the 2000 server

>>> because of "an error in the licensing protocol". I have made

>>> the registry entry for the license server on the Windows 2000

>>> server but error 1004 still appears in the event log. The XP

>>> clients should still be able to connect to the 2000 server

>>> without a purchased CAL should they not? TIA

[Guest Jim]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

Hi,

 

The Windows 2000 server used to be its own licensing server as part of a

work group so that may be why there are no existing licenses listed.

However it is not locating the new licensing server:

 

"The terminal services could not locate a license server. Confirm that

all license servers on the network are registered in WINS\DNS, accepting

network requests, and the Terminal Services Licensing Service is running"

 

I ran LSVIEW on it and there is no listed server. Can you suggest how I

can troubleshoot or force detection of the licensing server? I can

rebuild the database but I'm not sure that will help if the 2k server is

not locating the 2k3 license server.

 

TIA

 

 

Vera Noest [MVP] wrote:

> Well, at least we seem to have the cause of the problem:

>> There are no existing Windows 2000 licenses listed on the

>> licensing server.

> But I have no idea why these built-in licenses aren't there. I've

> no real good solution either, except that I would reinstall the LS.

>

> 273566 - How to rebuild Windows 2000 and 2003 Terminal Services

> Licensing database

> http://support.microsoft.com/?kbid=273566

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> *----------- Please reply in newsgroup -------------*

>

> Jim <nospam@any.time> wrote on 02 okt 2007:

>

>> They are XP Pro clients. The licensing server is activated.

>>

>> There are no existing Windows 2000 licenses listed on the

>> licensing server.

>>

>> There are two "Windows Server 2003 - Terminal Server Per Device

>> CAL Token" listings one for 5 and one for 25, all of which have

>> been issued.

>>

>> Temporary licenses have been issued as recently as last Thursday

>> from "Temporary Licenses for Windows 2003 Server - Terminal

>> Server Per Device CAL Token"

>>

>> I don't think there are related events in the licensing server

>> log, but the Windows 2000 TS log has 1003, 1004, 1010 in that

>> order when I try to connect, so it appears the licensing server

>> is not being located.

>>

>>

>>

>> TP wrote:

>>> Hi,

>>>

>>> XP Pro clients should receive a free TS CAL from the built-in

>>> pool when connecting to a 2000 TS. XP Home clients will *not*.

>>> When you open up TS Licensing (licmgr.exe) and connect to your

>>> 2003 TS Licensing server, what do you see?

>>>

>>> - Is the server activated?

>>> - Have any temporary licenses been issued? If so, from what

>>> pool (post the precise Product name)?

>>> - Have any permanent licenses been issued?

>>>

>>> On your 2003 TS licensing server, what errors/warnings appear

>>> in the System log, with a source of TermServLicensing?

>>>

>>> On your 2000 TS, what licensing-related errors/warnings appear

>>> in the System log with a source of TermService? Please post

>>> the Description field as well, because this will differ

>>> depending on the cause.

>>>

>>> For example, look for Event IDs 1004, 1008, 1010, 1011, 1026

>>>

>>> Thanks.

>>>

>>> -TP

>>>

>>> Jim wrote:

>>>> Hi,

>>>> I have a Windows 2000 terminal server that is part of a domain

>>>> where the TS license server is a Windows 2003 server. Windows

>>>> XP clients are being refused connections to the 2000 server

>>>> because of "an error in the licensing protocol". I have made

>>>> the registry entry for the license server on the Windows 2000

>>>> server but error 1004 still appears in the event log. The XP

>>>> clients should still be able to connect to the 2000 server

>>>> without a purchased CAL should they not? TIA

[Guest Jim]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

Aha. I went to your (excellent) Web site and found out that I was using

the licensing server registry value for a Windows 2003 terminal server

and not the (different) value for a Windows 2000 terminal server.

Logging in after setting that value -

http://support.microsoft.com/?kbid=239107 - has created an "existing

license" entry on the licensing server and LSVIEW shows the correct LS,

so hopefully that's fixed it. Thanks!

 

Jim wrote:

> Hi,

>

> The Windows 2000 server used to be its own licensing server as part of a

> work group so that may be why there are no existing licenses listed.

> However it is not locating the new licensing server:

>

> "The terminal services could not locate a license server. Confirm that

> all license servers on the network are registered in WINS\DNS, accepting

> network requests, and the Terminal Services Licensing Service is running"

>

> I ran LSVIEW on it and there is no listed server. Can you suggest how I

> can troubleshoot or force detection of the licensing server? I can

> rebuild the database but I'm not sure that will help if the 2k server is

> not locating the 2k3 license server.

>

> TIA

>

>

> Vera Noest [MVP] wrote:

>> Well, at least we seem to have the cause of the problem:

>>> There are no existing Windows 2000 licenses listed on the

>>> licensing server.

>> But I have no idea why these built-in licenses aren't there. I've no

>> real good solution either, except that I would reinstall the LS.

>>

>> 273566 - How to rebuild Windows 2000 and 2003 Terminal Services

>> Licensing database

>> http://support.microsoft.com/?kbid=273566

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> *----------- Please reply in newsgroup -------------*

>>

>> Jim <nospam@any.time> wrote on 02 okt 2007:

>>

>>> They are XP Pro clients. The licensing server is activated.

>>>

>>> There are no existing Windows 2000 licenses listed on the

>>> licensing server.

>>> There are two "Windows Server 2003 - Terminal Server Per Device

>>> CAL Token" listings one for 5 and one for 25, all of which have

>>> been issued.

>>> Temporary licenses have been issued as recently as last Thursday

>>> from "Temporary Licenses for Windows 2003 Server - Terminal

>>> Server Per Device CAL Token"

>>>

>>> I don't think there are related events in the licensing server

>>> log, but the Windows 2000 TS log has 1003, 1004, 1010 in that

>>> order when I try to connect, so it appears the licensing server

>>> is not being located.

>>>

>>>

>>> TP wrote:

>>>> Hi,

>>>>

>>>> XP Pro clients should receive a free TS CAL from the built-in

>>>> pool when connecting to a 2000 TS. XP Home clients will *not*.

>>>> When you open up TS Licensing (licmgr.exe) and connect to your

>>>> 2003 TS Licensing server, what do you see?

>>>>

>>>> - Is the server activated?

>>>> - Have any temporary licenses been issued? If so, from what

>>>> pool (post the precise Product name)?

>>>> - Have any permanent licenses been issued?

>>>>

>>>> On your 2003 TS licensing server, what errors/warnings appear

>>>> in the System log, with a source of TermServLicensing?

>>>>

>>>> On your 2000 TS, what licensing-related errors/warnings appear

>>>> in the System log with a source of TermService? Please post

>>>> the Description field as well, because this will differ

>>>> depending on the cause.

>>>> For example, look for Event IDs 1004, 1008, 1010, 1011, 1026

>>>>

>>>> Thanks.

>>>>

>>>> -TP

>>>>

>>>> Jim wrote:

>>>>> Hi,

>>>>> I have a Windows 2000 terminal server that is part of a domain

>>>>> where the TS license server is a Windows 2003 server. Windows

>>>>> XP clients are being refused connections to the 2000 server

>>>>> because of "an error in the licensing protocol". I have made

>>>>> the registry entry for the license server on the Windows 2000

>>>>> server but error 1004 still appears in the event log. The XP

>>>>> clients should still be able to connect to the 2000 server

>>>>> without a purchased CAL should they not? TIA

[Guest Vera Noest [MVP]]

Re: XP clients cannot connect to 2000 TS with 2003 license server

 

Great! I'm glad that you solved the problem, and thanks for sharing

the solution with us, Jim!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Jim <nospam@any.time> wrote on 02 okt 2007 in

microsoft.public.windows.terminal_services:

> Aha. I went to your (excellent) Web site and found out that I

> was using

> the licensing server registry value for a Windows 2003

> terminal server

> and not the (different) value for a Windows 2000 terminal

> server. Logging in after setting that value -

> http://support.microsoft.com/?kbid=239107 - has created an

> "existing license" entry on the licensing server and LSVIEW

> shows the correct LS, so hopefully that's fixed it. Thanks!

>

> Jim wrote:

>> Hi,

>>

>> The Windows 2000 server used to be its own licensing server as

>> part of a work group so that may be why there are no existing

>> licenses listed. However it is not locating the new licensing

>> server:

>>

>> "The terminal services could not locate a license server.

>> Confirm that all license servers on the network are registered

>> in WINS\DNS, accepting network requests, and the Terminal

>> Services Licensing Service is running"

>>

>> I ran LSVIEW on it and there is no listed server. Can you

>> suggest how I can troubleshoot or force detection of the

>> licensing server? I can rebuild the database but I'm not sure

>> that will help if the 2k server is not locating the 2k3 license

>> server.

>>

>> TIA

>>

>>

>> Vera Noest [MVP] wrote:

>>> Well, at least we seem to have the cause of the problem:

>>>> There are no existing Windows 2000 licenses listed on the

>>>> licensing server.

>>> But I have no idea why these built-in licenses aren't there.

>>> I've no real good solution either, except that I would

>>> reinstall the LS.

>>>

>>> 273566 - How to rebuild Windows 2000 and 2003 Terminal

>>> Services Licensing database

>>> http://support.microsoft.com/?kbid=273566

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> *----------- Please reply in newsgroup -------------*

>>>

>>> Jim <nospam@any.time> wrote on 02 okt 2007:

>>>

>>>> They are XP Pro clients. The licensing server is activated.

>>>>

>>>> There are no existing Windows 2000 licenses listed on the

>>>> licensing server.

>>>> There are two "Windows Server 2003 - Terminal Server Per

>>>> Device CAL Token" listings one for 5 and one for 25, all of

>>>> which have been issued.

>>>> Temporary licenses have been issued as recently as last

>>>> Thursday from "Temporary Licenses for Windows 2003 Server -

>>>> Terminal Server Per Device CAL Token"

>>>>

>>>> I don't think there are related events in the licensing

>>>> server log, but the Windows 2000 TS log has 1003, 1004, 1010

>>>> in that order when I try to connect, so it appears the

>>>> licensing server is not being located.

>>>>

>>>>

>>>> TP wrote:

>>>>> Hi,

>>>>>

>>>>> XP Pro clients should receive a free TS CAL from the

>>>>> built-in pool when connecting to a 2000 TS. XP Home clients

>>>>> will *not*. When you open up TS Licensing (licmgr.exe) and

>>>>> connect to your 2003 TS Licensing server, what do you see?

>>>>>

>>>>> - Is the server activated?

>>>>> - Have any temporary licenses been issued? If so, from what

>>>>> pool (post the precise Product name)?

>>>>> - Have any permanent licenses been issued?

>>>>>

>>>>> On your 2003 TS licensing server, what errors/warnings

>>>>> appear in the System log, with a source of

>>>>> TermServLicensing?

>>>>>

>>>>> On your 2000 TS, what licensing-related errors/warnings

>>>>> appear in the System log with a source of TermService?

>>>>> Please post the Description field as well, because this will

>>>>> differ depending on the cause.

>>>>> For example, look for Event IDs 1004, 1008, 1010, 1011, 1026

>>>>>

>>>>> Thanks.

>>>>>

>>>>> -TP

>>>>>

>>>>> Jim wrote:

>>>>>> Hi,

>>>>>> I have a Windows 2000 terminal server that is part of a

>>>>>> domain where the TS license server is a Windows 2003

>>>>>> server. Windows XP clients are being refused connections to

>>>>>> the 2000 server because of "an error in the licensing

>>>>>> protocol". I have made the registry entry for the license

>>>>>> server on the Windows 2000 server but error 1004 still

>>>>>> appears in the event log. The XP clients should still be

>>>>>> able to connect to the 2000 server without a purchased CAL

>>>>>> should they not? TIA