We help IT Professionals succeed at work.

Licensing Protocal error running RDP on local Vista client and Win 2000 Server

Last Modified: 2013-11-21
Windows Vista Ultimate gets "licensing protocol" error running Remote Desktop Connection. RDC did connect to local Win 200 Server and only recently began getting this error. A fresh install of vista on this client does work so I copied the MSlicensing key to the troubled instal - but no luck. Other Vista and Xp clients on the local network connect with RDP OK. Wondering what other areas of registery or services relate to RDP that I should check to avoid re-install of Vista & all programs?
Watch Question

1. Verify that the license server is correctly installed.
2. Verify that the Terminal Server Licensing service is running on the license server.
3. Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
4. On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.

If above didnt solve try these ....
1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
2. Click MSLicensing.
3.  On the Registry menu, click Export Registry File.
4. In the File name box, type mslicensingbackup, and then click Save.
5.  If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
6 On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
7.  Close Registry Editor, and then restart the computer


RDP on other Vista and XP machines on the local network work OK with the Win 2000 Server - so this is a problem with ONE Vista client machine.

The problem client machine does work if Vista is re-installed so I suspect the problem is in corrupt registry.

Vista does not rebuild the MSlicensing key as does XP - and so the above info deos not seem to apply to Vista.

My objective is to find the problem with RDP and avoid re-installing Vista and the many applications installed on the client.


UPDATE: I resolved the issue and believe the problem was caused by Norton 360 software installed -  Norton 360 (without some special attention) is not compatible.  This is fine with me as I am giving up on Symantec entirely as a vendor since I've had problems with every version of Ghost, Systemworks & password manager released in the past 5 or more years. Seems better alternatives always exist elsewhere.
This one is on us!
(Get your first solution completely free - no credit card required)

You may download a free tool at www.digitalsupporttech.com. The tool will tell you what causes the problem. It is also free to get it fixed.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.