Home > Licensing Protocol > Remote Desktop Licensing Protocol Error Windows Xp

Remote Desktop Licensing Protocol Error Windows Xp

Contents

If you are not sure how to delete the key and its subkeys, just rename them as follows : HardwareID to HardwareID-temp and Store to Store-temp. 4> Reboot the system. or Delete the MSLisencing "HKLM\Software\microsoft\Mslicensing"key from the workstation and reboot it. Windows XP – simply run Remote Desktop Connection 5. You should now be able to connect to your 2008 per user licensed terminal server. http://supercgis.com/licensing-protocol/remote-desktop-error-in-licensing-protocol-windows-xp.html

Right Click RDC and run as administrator, this will reset you RDC and give you a new license. Please try connecting to the remote computer again or contact your server administrator." The Microsoft knowledge base had this to say "Cause: The licensing protocol handles the communication of licensing information I hope Tuesday will give me some means of testing this further with the updates. 1317-315687-1689256 Back to top J.R. Thursday, August 11, 2011 8:16 PM Reply | Quote 0 Sign in to vote this worked for me, as I am the admin.

The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol

Thanks. -TP Thursday, May 19, 2011 9:28 PM Reply | Quote Moderator 0 Sign in to vote You say there's no Firewall service on the server, is there a firewall between Is the ability to finish a wizard early a good idea? Uninstalling Terminal Services should fix the issue.

Note: You only need to this the first time. We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions. Once I get going on upgrading the image however, I'm going to also include other Windows updates, verify the ICA settings (since one server misbehaved today, which might be contributed to Change The Terminal Server Licensing Mode From Per Device To Per User Charles May 21, 2010 at 4:59 am great!

On 2 identical built machines > >> >> > (e.g. The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008 License server role installed. Please re-enable javascript to access full functionality. http://www.techbuzz.in/how-to-fix-the-remote-computer-disconnected-the-session-because-of-an-error-in-the-licensing-protocol.php TY pelop April 29, 2014 at 7:16 pm | PermalinkIt works for Windows 8,1 x64 many thanks for the solution Hetal June 17, 2014 at 2:15 am | Permalinkyou are genius!!!!It

But, after tried the > solution, problem still there. Mslicensing Key Thanks.. In this one-day training, you'll find out what this new model for Windows really means to your organization and what the benefits are once you've made the move to Windows 10. Disable write protect. (There is a shortcut for it on the desktop.) System will restart automatically.Logon to Wyse terminal administrator again.

The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008

It's VERY important that you run the Remote Desktop Connection Manager as administrator in order for it to work. please note all other Windows workstations do not get the licensing protocol error from the Server. The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol If you continue to receive this error message, contact the server administrator" Well here's the solution to fix this problem: This actually is a registry fix. The Remote Computer Disconnected Session Licensing Protocol Windows 7 Setup your RDP session for your terminal server.

Gautam H N May 4, 2009 at 7:36 pm @ Softwaresnhard - I don't see a reason why this would not work .. weblink I guess when the guy set up the > > machine with W2k server. Joe July 7, 2010 at 6:31 pm Hi, had this problem overnight on Windows 7, my user account is an admin but the recreation of keys wasn't working. Best Chass January 14, 2010 at 12:41 am I'm running Vista Home trying to fix the same problem with a users computer. Remote Session Was Disconnected Because There Are No

Recommended reading: Registry tweak to improve performance of Windows XP SHARE Facebook Twitter tweet Gautam RELATED ARTICLESMORE FROM AUTHOR How To's How to Remove Shortcut Virus from Pendrive How To's Recover All Rights Reserved Privacy & Terms Skip to Navigation Skip to Content Windows IT Pro Search: Connect With Us TwitterFacebookGoogle+LinkedInRSS IT/Dev Connections Forums Store Register Log In Display name or email Gautam February 4, 2010 at 12:10 pm @Narayanan - Whats the environment you are working in ? navigate here Have used TS for years and never saw this error.

The error in licensing protocol is almost exclusively seen in Per Device environments. Mslicensing Registry Key Missing Remote desktop role installed. It did not recreate the licensing keys.

Even more strange is that there was no alteration in the permissions on the registry keys after trying this connect.Eventho the user has indirect membership (through a group) of the 'Remote

The person who > set this up no longer with our company and I'm not sure how he > installed the licenses. > > Any suggestion will be highly regarded. > Same with an application and a database server. Thanks narayanan February 4, 2010 at 3:18 pm Windows 7 is my system. Hkey_local_machine\software\microsoft\mslicensing Guillaume December 10, 2013 at 1:43 am | PermalinkYou are my saver !!!

I did check into http://forums.citrix...ssageID=1570941 as a possible solution, but in my situation that doesn't do anything. Please try connecting to the remote computer again or contact your server administrator. Hello and welcome to PC Review. his comment is here If a client > > was successfully connected, this event won't be generated. > > > > I didn't hardcode the "DefaultLicenseServer" and there is no > > such key in

The event ID is 1004 which > means the server failed to contact the license server to renew a > license. Liger August 4, 2010 at 12:02 am @Joe I had this problem on windows 7 and I run as admin and recreated the deleted keys. Cheers, ben February 4, 2011 at 4:47 am I just wanted to make sure when you said "delete the MSLicensing key", you meant the whole folder or just the registry file But, we definitely installed a certificate for > the server itself.

I get a desktop, and I can enter my logon credentials for that server. About Us PC Review is a computing review website with helpful tech support forums staffed by PC experts. Dell >> > GX280) and both running WinXP SP2, one can and one can't >> > connect to this TS. Thank you!

next time when you logon Pullup the RDC with Elevated Rights --> RDc --Right click---Run as Admin. Do I need to turn off camera before switching auto-focus on/off? Infact they are in the same room on the same switch. Name * Email * Website Every Home Needs a Harvey LatestCommentsCategoriesBookmarksSpace OddityGun Free ZonesDog HumorPaper is NOT Dead!Passwords SuckCaden And ConnorHormones, Or How To Communicate With WomenPearl Harbor After Visiting HoursOne

On 2 identical built machines (e.g. I have also tried: mstsc -console without any luck. van Doornik 17 posts Posted 20 November 2012 - 01:14 PM The exact changes I made, as depicted in the article:Changing the Default Unfiltered User Policy Settings for ICA in the van Doornik , 30 October 2012 - 08:56 AM Login to Reply 19 replies to this topic J.R.

thanks! Reboot the computer. Advertisement Join the Conversation Get answers to questions, share tips, and engage with the IT professional community at myITforum. Publish Related resources SolvedLicensing Protocol Error Forum Error in licensing protocol windows 7 Forum Licensing Protocol Error Forum Licensing Protocol Forum SolvedERR_QUIC_PROTOCOL_ERROR.

may be there are situations when it doesn't. The exact error message is: "The remote >> > computer disconnected the session because of an error in the >> > licensing protocol. share|improve this answer answered Aug 17 '09 at 9:21 mrdenny 25.4k33163 add a comment| up vote 0 down vote If you don't install a Terminal Licencing Server within 120(?) days of Thanks, Dom "Vera Noest [MVP]" wrote: > No, you should not have to hardcode the DefaultLicenseServer, I > only mentioned this because it is part of the troubleshooting tips > that