W2KTS problem of '.an error in the licensing protocol' at Srv03 Do

[Guest Rulf Tse]

Several days before, some of the existing TS users could not connect to a W2K

TS Server with the following message. It is located at a Srv03 Domain while

the TS Licensing Server is at 1 of the Srv03 Domain Controller.

 

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

 

I have done the steps from TechNet and Support sites:

1. Removing the TS client's registry.

2. Removing the TS Licensing Server.

3. Reinstall the TS Licensing Server for connection.

The problem stills exist even if I restored the workable OS image of several

months ago.

 

I find that this machine does not accept any connection from the new client

machine that has not logged on before and the rejected existing client

machine is increasing. At the System Event, there is a log of ID 1004, 'The

terminal server cannot issue a client license. '

 

HELP! HELP! HELP!

[Guest Munindra Das [MSFT]]

Re: W2KTS problem of '.an error in the licensing protocol' at Srv03 Do

 

The recommended way is to deploy 2003 license servers with 2003 DCs. The

article at http://support.microsoft.com/kb/823313 explains the process. I am

cut pasting the main part here:

 

When you deploy Windows Server 2003 Terminal Services in a Windows 2000

domain, you have the following licensing options:

• Upgrade existing Windows 2000 domain controllers that host the Windows

2000 license server to Windows Server 2003 domain controllers.

• Install Windows Server 2003 Terminal Server License Server on a member

server that is running Windows Server 2003.

• Demote the Windows 2000-based license server to a member server, upgrade

this computer to Windows Server 2003, and then add additional domain

controllers as required.

 

But if you do not want to upgrade, the article at

http://technet2.microsoft.com/windowsserver/en/library/ca7c771f-26ad-4308-8912-12778d6f454e1033.mspx?mfr=true

will provide more info on what to do. Following is the relevant piece:

 

Windows 2003 domain: Windows 2000 terminal servers and Windows 2000 license

servers

• If the license server and the terminal server are not already running

Windows 2000 SP4, install this service pack on both computers. To download

SP4, see Windows 2000 Service Packs

(http://go.microsoft.com/fwlink/?LinkId=48213), on the Microsoft Web site.

 

• On the Windows 2000 license server, apply the hotfix described in article

837321, You cannot connect to a Windows 2000 Terminal server if your Windows

Server 2003 Terminal Services license is expired

(http://go.microsoft.com/fwlink/?LinkId=48215), on the Microsoft Web site.

 

• On the Windows 2000 terminal server, apply the hotfix described in article

829395, The Terminal server does not automatically shut down when the

TSShutdn.exe command is invoked in Windows 2000

(http://go.microsoft.com/fwlink/?LinkId=48216), on the Microsoft Web site.

 

If the failure you are noticing is because of TS server not being able to

detect the License Server (LS), it will solve it. The process to set default

license server on a Windows 2003 TS server is:

To select a specific license server, follow these steps, and then quit

Registry Editor.

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters

3. On the Edit menu, point to New, and then click Key.

4. Name the new key "LicenseServers"

5. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers

6. For each licensing server to which you would like to point the Terminal

Services server, point to New on the Edit menu, and then click Key.

7. Name the new key "ServerName" where ServerName is the NetBIOS name of the

license server that you want to use, and then press ENTER.

 

Note The new key name can be any of the following designations that

represent the license server: • The NetBIOS name of the server

• The fully qualified domain name (FQDN) of the server

• The IP Address of the server

 

8. Restart your computer.

 

 

 

 

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Rulf Tse" <Rulf Tse@discussions.microsoft.com> wrote in message

news:D9FD030F-ED2F-4E3E-8CC2-8170D48F241F@microsoft.com...

> Several days before, some of the existing TS users could not connect to a

> W2K

> TS Server with the following message. It is located at a Srv03 Domain

> while

> the TS Licensing Server is at 1 of the Srv03 Domain Controller.

>

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

>

> I have done the steps from TechNet and Support sites:

> 1. Removing the TS client's registry.

> 2. Removing the TS Licensing Server.

> 3. Reinstall the TS Licensing Server for connection.

> The problem stills exist even if I restored the workable OS image of

> several

> months ago.

>

> I find that this machine does not accept any connection from the new

> client

> machine that has not logged on before and the rejected existing client

> machine is increasing. At the System Event, there is a log of ID 1004,

> 'The

> terminal server cannot issue a client license. '

>

> HELP! HELP! HELP!

>