Error In Licensing Protocol
Contents |
and Other Interesting Information... Windows 7: Remote Desktop error in the licensing protocol Posted by Ivan Versluis / April 3, 2012 / 10 Comments Windows 7 is running Remote Desktop Protocol version 7 error in licensing protocol windows 7 (RDP 7). Since we are using Windows 7 we run into following problem. Remote error in licensing protocol windows 7 fix Desktop Connection - The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the
No Terminal Server License Servers Available To Provide A License
remote computer again or contact your server administrator. There was little valuable information on the Internet to solve this problem. To fix this problem a client was reinstalled. In the end there was a simple solution fix
Error In The Licensing Protocol Vista
this problem to connect to remote systems. The problem was not on the remote desktop or terminal server but on the client itself. How to fix remote desktop error in licensing protocol? Right-click on "Remote Desktop Connection" shortcut in the Start Menu and click on "Run As Administrator" once. Logon as Administrator and connect to the remote system. Reboot the system and RDP session will work again. If the system is used by error in the licensing protocol remote desktop a regular user the connection will work now. References MSDN - Remote Desktop Connection 7 for Windows 7, Windows XP & Windows Vista Posted in Windows 7 July 24, 2013 Tony Kriskovich Ivan, Thanks for this! I spent too much time on this and to find out such a simple solution. Thanks again for the writeup! Tony August 21, 2013 JC Soucy Work for me to thanks December 17, 2013 Shane Wilkerson Worked man. Thanks for the info February 2, 2014 rajesh thanks man god bless you……. February 15, 2014 Tausif Still having issue while log in via administrator March 10, 2014 Gaurav Thank you so much August 11, 2014 Taip It works, thank you very much! October 29, 2014 Prasad You're awesome, Simple solution for a problem that i thought was complex. April 1, 2016 happy tHANKS……………………… Its Works April 15, 2016 raghu Simple step,but worked perfectly.. Leave a comment Click here to cancel reply. Name * Email * Website Comment Add Comment Notify me of followup comments via e-mail Sponsor Search Search for: Recent Posts PowerShell: Automate SSO configuration for SAP GUI August 12, 2016 Posted in PowerShell, SAP, SCCM Office 2016: Outlook cannot provide form scripting support June 29, 2016 Posted in Microsoft, Office
password Advertise News Mobile AllApplicationsIphoneWindows Phone Iphone iPhone stuck on Apple Logo - Fix Iphone iOS10 Tips and Tricks - Remove or Add Widgets from Home… Iphone Safari Running Slow on iOS10 - Fix Iphone How
Error In Licensing Protocol Windows 2000
to Fix Apps crashing in iOS 10 Beta Gadgets Design Photography Cell Phone / error in licensing protocol 2008 Mobile Utilities Best Apps for iPhone Photography Reviews Reviews Facebook versus Google Plus Reviews Battle of the tablets: Apple vs. Blackberry Reviews error in licensing protocol regedit Epson WorkForce 635 All-In-One Printer, Review, Price, Availability Reviews Hosting And Cost Of Doing Business Reviews Negative Things / Disadvantages About Apple iTouch Before You Buy One More Apple Android Windows Phone Iphone Home How To's http://www.networknet.nl/apps/wp/archives/2221 How to fix - The Remote Computer Disconnected the session because... How To'sMicrosoft Windows Tips And Tricks How to fix - The Remote Computer Disconnected the session because of an error in the Licensing protocol By Gautam - April 8, 2009 5523 58 Today, one of my client had problem while he was trying to connect to a remote computer to work. The remote desktop on his Windows XP (Related Post : http://www.techbuzz.in/how-to-fix-the-remote-computer-disconnected-the-session-because-of-an-error-in-the-licensing-protocol.php If you have MSLicensing Problem on Windows Vista, then check this post.) was running fine, but now he was getting this error: "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." When I looked up in the knowledge base, this is what Microsoft had to say : "Cause: The licensing protocol handles the communication of licensing information between your computer and the remote computer. If there is an error in the licensing protocol, your computer cannot be connected to the remote computer. Solution: Try connecting to the remote computer again. 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. You'll be prompted to delete a few keys and subkeys and hence it's better if you take a back up of your registry manually, so that you can restore it if something goes wrong during the process. If you do not know how to take back up of your registry manually follow this tutorial : Tutorial to to back up the registry in Windows Vista or in Windows XP. Once you have taken the back up, 1> Click on S
1 On the client, delete the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing key 2 On the client, run "Remote Desktop Connection" as administrator https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol (just one time) From then on, it can be run as http://www.kjctech.net/the-remote-computer-disconnected-the-session-because-of-an-error/ usual 1 Comment Pimiento nathanjackson Mar 23, 2015 at 01:44am I had this error on a new Windows 8.1 Pro workstation connecting to a pool of Windows 2012 R2 servers via RD Web access. This resolved the issue for me with the only difference being that error in I had to run RD Web access from an Internet Explorer window with elevated privileges instead of using the Remote Desktop Connection software. Read these next... Word of the week: Secure Sockets Layer, aka SSL Security What you need to know about SSL. Samsung kills off the Note 7 Water Cooler According to Bloomberg, "Samsung Electronics Co. is error in licensing ending production of its problematic Galaxy Note 7 smartphones, taking the drastic step of killing off a smartphone." Spark: Atomic Energy Agency says nuclear power plant was hacked Spiceworks Originals Your morning news, a Community wrap up, a lunch recommendation, and the funnies. © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with your email address First Name Last Name Email Join Now or Log In Email Password Log In Forgot your password? Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Join the community Back I agree Powerful tools you need, all for free. Help Desk » Inventory » Monitor » Community »
Kent Chen June 12, 2009 Tips & Tricks One remote user from work called me the other day saying her remote desktop client stopped working because of “there are no terminal server client access licenses available for this computerâ€. Well, that's easy, I walked her through and successfully deleted the MSLicensing registry key on her Windows Vista computer, and happily told her you can try it again now. But surprisingly, she replied a few seconds later saying no, still didn't work. But this time the error message was different: The remote computer disconnected the session because of an error in the licensing protocol It's surprising because having been using remote desktop client for ages this is the first time I saw the error message like this. Out of luck after a few checking here and there, I went to Google for help. Nothing had worked until I was landed to this Microsoft KB, Removing Terminal Server licenses from an RDP client. At the very bottom of this KB, it mentions: If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal Server may fail. Also, you receive the following error message: An Error occured in the licensing protocol. And suggests that to resolve this problem, right-click the Remote Desktop Connection icon, and then click Run as Administrator. Bingo!! That was it. Did I mention that this problem was actually occurred on a Vista computer above? And it only happens on Vista or later OSs because: By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys. Related Posts: Terminal License Will be Expired in x Days Remote Desktop Keyboard Shortcuts Remote Desktop (RDP) on iPhone You may also likeHow to make an old school SUBST virtual drive pe