Internal Error In Remote Licensing Protocol
Contents |
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for the remote computer disconnected the session because of an error in the licensing protocol 2012 Help Receive Real-Time Help Create a Freelance Project Hire for a the remote computer disconnected the session licensing protocol windows server 2008 Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products
The Remote Computer Disconnected Session Licensing Protocol Windows 7
BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The remote session was disconnected because there was an internal error
Change The Terminal Server Licensing Mode From Per Device To Per User
in the remote computers licensing protocol Want to Advertise Here? Solved The remote session was disconnected because there was an internal error in the remote computers licensing protocol Posted on 2010-07-22 MS Server OS Windows Server 2003 1 Verified Solution 7 Comments 4,417 Views Last Modified: 2013-11-21 Several machines which haven’t connected to the terminal the remote session was disconnected because there are no remote server before or had their named changed cannot connect with the error message: "The remote session was disconnected because there was an internal error in the remote computers licensing protocol" I have tried the registry edit removing the contents of: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store Which didn’t help. This is happening on several machines so it seems to be a problem on the server side. I have looked in the Terminal server licensing and the problem machines are showing as temporary licenses. Any ideas please. 0 Question by:robquartzelec Facebook Twitter LinkedIn Google Best Solution byrobquartzelec Our problem was solved by doing the following: Open regedit and erase the keys: HKLM\Software\Microsoft\TermServLicensing\Certificates. HKLM\System\CurrentControlSet\services\TermservLicensing\Parameters\Certificates.000 Go to Solution 7 Comments LVL 20 Overall: Level 20 Windows Server 2003 11 MS Server OS 7 Message Active today Expert Comment by:Radhakrishnan Rajayyan2010-07-22 Please find this article for step by step guide http://johndelizo.spaces.live.com/blog/cns!5686721B6E7BA618!403.entry 0 Message Author Comment by:robquartzelec2010-07-22 Thanks for the comment, but the server is allready setup for peop
and Other Interesting Information... Windows 7: Remote Desktop error in the licensing protocol Posted by Ivan Versluis / April 3, 2012 /
Mslicensing Registry Key Missing
10 Comments Windows 7 is running Remote Desktop Protocol version 7 (RDP the remote session was disconnected because license store creation failed with access denied 7). Since we are using Windows 7 we run into following problem. Remote Desktop Connection - The remote computer mslicensing key disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. There was little valuable information on https://www.experts-exchange.com/questions/26348605/The-remote-session-was-disconnected-because-there-was-an-internal-error-in-the-remote-computers-licensing-protocol.html the Internet to solve this problem. To fix this problem a client was reinstalled. In the end there was a simple solution fix 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 http://www.networknet.nl/apps/wp/archives/2221 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 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
we highly recommend that you visit our Guide for New Members. Solved: Remote Desktop Connection trouble Discussion in 'Windows Vista' started by barrypatch, Jun 15, 2011. Thread Status: Not open for further replies. Advertisement https://forums.techguy.org/threads/solved-remote-desktop-connection-trouble.1002377/ barrypatch Thread Starter Joined: Sep 10, 2004 Messages: 190 I am unable to log into https://community.spiceworks.com/how_to/40598-fix-remote-session-was-disconnected-because-there-are-no-remote-desktop-client-access-licenses the remote desktop of one of our clients, I get the licensing protocol error. Their support staff says it is on my end and keeps sending me things to try. I log into their VPN, then RDC. If the remote computer is the one having the licensing protocol issues, doesn't that mean there is nothing on my end that can be done? the remote I have searched all morning and found similar issues, people deleting the registry key, tried that and it didn't work. They told me to right click on the connection and log in as admin. I am using VISTA, by the way. I don't have that choice. They said then I am not an administrator. But, it shows I am the admin. I went to the microsoft support site and did the Mr. Fix It thing and that the remote computer didn't fix it. I might be crazy, but I was thinking the problem at to be on their end. I think I have gotten this before or some of our employees. I was working in there fine yesterday, logged out and now can't get back in. I tried another facility from that same client, but a totally different region and was able to log in. I am thinking that the problem is specifically on their end. She insists it's not because no one else has complained. One other person (from our company) who works using that same connection is able to log in fine, so I don't know. This is beyond frustrating. Any ideas? Thanks. Nan barrypatch, Jun 15, 2011 #1 Sponsor Squashman Trusted Advisor Joined: Apr 4, 2003 Messages: 19,764 barrypatch said: ↑ I have searched all morning and found similar issues, people deleting the registry key, tried that and it didn't work. They told me to right click on the connection and log in as admin. I am using VISTA, by the way. I don't have that choice. They said then I am not an administrator. But, it shows I am the admin.Click to expand... You may be an administrator but it is not running it as Administrator. You need to right click on MSTSC.exe or a shortcut to that file and select Run as Adm
following error message with Remote Desktop ConnectionDesktop ConnectionDesktop Connection when you try to connect to a machine: “Remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator“ Steps (3 total) 1 The solution is delete the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing The solution is delete the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing 2 Try connecting in again If it doesn’t work and you get the following error message: “The remote computer disconnected the session because of an error in the licensing protocol“; 3 Still does not work? Then all you need to do is Right-Click on the Remote Desktop Connection icon and select “Run as Administrator“. References Fix – Remote session was disconnected because there are no Remote Desktop client access licenses 25 Comments Mace hsc5775 Jun 19, 2013 at 07:00am #3 The "Run as Administrator" option is always a good trick. thx for share Sonora Moree Aug 5, 2013 at 02:49am Thanks! Its perfectly work with "Run as Administrator" step. This trick seems like a joke from Microsoft to IT support. A good start on this beautiful Monday. Chipotle Guy 6779 Jan 23, 2014 at 12:24am I know it's a pretty easy fix, what i want to know is what causes the issue ? Pimiento Sludg3 May 13, 2014 at 12:56pm Hi guys , under MS licensing i have HardwareID and Store sub folders , should i remove these too? Tabasco WouterNel May 13, 2014 at 01:20pm Delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing and all its contents. When you reconnect with RDP the key will be recreated! Pimiento jeremy63 Jul 30, 2014 at 12:57pm Should I delete the registry key on the server side, or on the client's computer that connects to the server? Tabasco WouterNel Jul 31, 2014 at 08:36am jeremy63, Only on the client computer and then run RDP as Administrator. Pimiento toyinfolarin Sep 3, 2014 at 12:11pm hi guys, i tried out these options listed (HKEY deletion and running as administrator), i couldnt connect still to the WMS 2012 running on the server machine. could this be because i was not able t