Licensing Problem

[Guest Lesa H.]

have a client who has SBS 2003 R2 with a Server 2000 server in Application

Sharing mode behind it. They have quite a few users that are connecting to

the terminal server remotely. The SBS server is the licensing server for the

terminal. I just started getting reports that some of the users are

receiving messages as follows:

 

"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."

 

Another error message is also generated about remote license being expired

but I don't have the exact verbiage on that one. When I check terminal

licensing on the SBS server, there are a total of 29 licenses - 16 listed as

Built-in and 13 listed as temporary (these are the people that are getting

the licensing expiration and/or protocol errors). All users are using at

least Windows 2000 with a mix of XP Home and Pro but mostly XP Home.

 

On the Terminal Server we're getting the following errors quite a few times

a day:

 

Event Type: Warning

Event Source: License

Event ID: 213

Computer: TRMSVR

Description:

Replication of license information failed because the License Logging

Service on server \\SERVER1 could not be contacted.

 

How do I go about resolving this? It's my understanding the with the Windows

2000 server acting as a terminal server, TS CAL's are not required. I've

tried Googling the issue without resolution.

 

Thanks in advance.

[Guest TP]

Re: Licensing Problem

 

Hi,

 

When connecting to your 2000 TS from an XP Home device a

*purchased* TS CAL is required. From your description it

appears that you don't have any purchased TS CALs installed

on your TS license server.

 

-TP

 

Lesa H. wrote:

> have a client who has SBS 2003 R2 with a Server 2000 server in

> Application Sharing mode behind it. They have quite a few users that

> are connecting to the terminal server remotely. The SBS server is the

> licensing server for the terminal. I just started getting reports

> that some of the users are receiving messages as follows:

>

> "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."

>

> Another error message is also generated about remote license being

> expired but I don't have the exact verbiage on that one. When I check

> terminal licensing on the SBS server, there are a total of 29

> licenses - 16 listed as Built-in and 13 listed as temporary (these

> are the people that are getting the licensing expiration and/or

> protocol errors). All users are using at least Windows 2000 with a

> mix of XP Home and Pro but mostly XP Home.

>

> On the Terminal Server we're getting the following errors quite a few

> times a day:

>

> Event Type: Warning

> Event Source: License

> Event ID: 213

> Computer: TRMSVR

> Description:

> Replication of license information failed because the License Logging

> Service on server \\SERVER1 could not be contacted.

>

> How do I go about resolving this? It's my understanding the with the

> Windows 2000 server acting as a terminal server, TS CAL's are not

> required. I've tried Googling the issue without resolution.

>

> Thanks in advance.

[Guest Lesa H.]

Re: Licensing Problem

 

TP,

 

Thanks for the response.

 

I see, that may be the source of the problem. I'll check with the users and

find out for sure what OS they are using. Does this only apply to connecting

to the Terminal server? If they were to connect to a Windows XP unit, this

wouldn't apply, correct?

 

 

"TP" <tperson.knowspamn@mailandnews.com> wrote in message

news:ervDgL97HHA.3940@TK2MSFTNGP05.phx.gbl...

> Hi,

>

> When connecting to your 2000 TS from an XP Home device a *purchased* TS

> CAL is required. From your description it appears that you don't have any

> purchased TS CALs installed on your TS license server.

>

> -TP

>

> Lesa H. wrote:

>> have a client who has SBS 2003 R2 with a Server 2000 server in

>> Application Sharing mode behind it. They have quite a few users that

>> are connecting to the terminal server remotely. The SBS server is the

>> licensing server for the terminal. I just started getting reports

>> that some of the users are receiving messages as follows:

>>

>> "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."

>>

>> Another error message is also generated about remote license being

>> expired but I don't have the exact verbiage on that one. When I check

>> terminal licensing on the SBS server, there are a total of 29

>> licenses - 16 listed as Built-in and 13 listed as temporary (these

>> are the people that are getting the licensing expiration and/or

>> protocol errors). All users are using at least Windows 2000 with a

>> mix of XP Home and Pro but mostly XP Home. On the Terminal Server we're

>> getting the following errors quite a few

>> times a day:

>>

>> Event Type: Warning

>> Event Source: License

>> Event ID: 213

>> Computer: TRMSVR

>> Description:

>> Replication of license information failed because the License Logging

>> Service on server \\SERVER1 could not be contacted.

>>

>> How do I go about resolving this? It's my understanding the with the

>> Windows 2000 server acting as a terminal server, TS CAL's are not

>> required. I've tried Googling the issue without resolution.

>>

>> Thanks in advance.

[Guest TP]

Re: Licensing Problem

 

You are welcome.

 

Correct, when connecting to a Windows XP Pro machine

via Remote Desktop a TS CAL is not required. Depending

on your version of XP the End User Licensing Agreement

will vary as to the requirements for connecting via RD. Please

see the EULA if you are interested in a very specific answer.

 

-TP

 

Lesa H. wrote:

> TP,

>

> Thanks for the response.

>

> I see, that may be the source of the problem. I'll check with the

> users and find out for sure what OS they are using. Does this only

> apply to connecting to the Terminal server? If they were to connect

> to a Windows XP unit, this wouldn't apply, correct?