Mstsc Error In Licensing Protocol
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 00:15:12 GMT by s_wx1011 (squid/3.5.20)
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 to Fix Apps crashing in
The Remote Session Was Disconnected Because There Are No Remote Desktop License
iOS 10 Beta Gadgets Design Photography Cell Phone / Mobile Utilities Best Apps for iPhone Photography
Mslicensing Key
Reviews Reviews Facebook versus Google Plus Reviews Battle of the tablets: Apple vs. Blackberry Reviews Epson WorkForce 635 All-In-One Printer, Review, Price, Availability hkey_local_machine\software\microsoft\mslicensing 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 How to fix - The Remote Computer Disconnected the session http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/remote-desktop-connection-error-message-the-remote/cc914f39-3d8e-4671-b569-b1ba5d68b380 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 5970 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 : If you have MSLicensing Problem on Windows Vista, then check this post.) was running fine, but http://www.techbuzz.in/how-to-fix-the-remote-computer-disconnected-the-session-because-of-an-error-in-the-licensing-protocol.php 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 Start Menu -> Go to Run Command box -> Type regedit -> This opens the registry Editor. 2> Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing 3> Delete all the keys under MSLicensing : both HardwareID and Sto
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting http://serverfault.com/questions/54893/remote-desktop-to-win-2008-error-in-license-protocol ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask http://jeffpicard.com/blog/computer-fixes/microsoft-remote-desktop-licensing-fix/ a question Anybody can answer The best answers are voted up and rise to the top Remote Desktop to Win 2008: Error in License protocol up vote 0 down vote favorite I am sitting on a Win XP machine trying to connect the remote to a Windows 2008 Server. I think the cause of this issue might be due to the fact that I said yes to install a terminal server back when I installed the server as I didn't know it wasn't nessecary for RDP. I don't know if this i9s what is blocking the connection but something is. The error message (translated from danish): "The remote computer disconnected the session due to an error in the licensing protocol. Try again or contact serveradministrator." Now the the remote computer real issue here is that I can't remote desktop and fix the error. I have also tried: mstsc -console without any luck. Any suggestions are welcome :) windows windows-server-2008 share|improve this question asked Aug 17 '09 at 9:10 user16966 11615 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote You can try rebooting the server, but you'll need to check on the license server to see if there are any errors. If you installed Windows 2008 in Terminal Server mode you'll need to get on the server and remove Terminal Services in order to get the admin RDP working again. You probably don't have any Terminal Service licenses to use. 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 installing the Terminal Server service, Terminal Services will cease to operate. And of course, once you do install a license server, you need to install licenses! However, this should not stop you from using the /console switch (although keep in mind, if this is vista, its been renamed to /admin) just as long as the Allow Remote Desktop Connections is ticked in the system properties. Unfortunately because of the translation of the message I can't match it to an exact message that I'm familiar with, but it sounds a lot like an issue with expired licenses, or no licensing server. share|improve this answ
Fixes / Remote Server Licensing Fix Remote Server Licensing FixIf you use Microsoft's Remote Desktop connection on a regular basis, there's a pretty good chance you've run into this problem: Eventually, you get an error that tells you that your Remote Desktop License will expire in "X" number of days. If you try to google a solution to this problem you'll be inundated with accusations that you're stealing the program and that you should go pay for a valid license. How can you be stealing something that is included with most modern versions of the Windows operating system? Without going into just why this happens, the solution is actually pretty easy. The following procedure is for either Windows Vista or Windows 7. Read below and follow the instructions closely:Click on the Start button and in the search box type "regedit" (without the quotes)The Regedit program should be highlighted at the top of the start window. Either simply hit ENTER, or double click it.In Regedit, navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensingRight click on the key name "MSLicensing" and select DELETE.Close RegeditDo NOT open any shortcuts for Remote Connections at this point. Instead, you need to open the Remote Desktop Connection Manager. It's VERY important that you do this by RIGHT clicking on the program and selecting "Run as administrator." If you don't do this properly, the registry key you deleted in step 4 will not be recreated. The Remote Desktop Connection Manager can be found at: START/All Programs/Accessories/Remote Desktop Connection.Select the remote connection you want to use and click "Connect." If you've done this properly, a new registry key will be added that will have updated licensing information.This fix will need to be redone on a somewhat regular basis. I think I've got to do this about two to three times a year. 42 Responses to "Remote Server Licensing Fix" Kanchana May 14, 2012 at 5:35 am | PermalinkThis is not fixing my issue in windows 7. Brandon May 17, 2012 at 3:37 pm | Permalinkdidnt work for me either Kanchana May 22, 2012 at 8:06 am | PermalinkIs there any other fix available for windows 7 professional Jeff May 22, 2012 at 10:33 am | PermalinkHey guys. I used this fix when my office was running Microsoft Server 2000.