Internal Error Licensing Protocol Remote Computer
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Remote Desktop Licensing Protocol error Windows Server > Remote Desktop Services (Terminal Services) Question 0 the remote computer disconnected the session because of an error in the licensing protocol windows 7 Sign in to vote I have spent the last 4 hours looking for solution online the remote computer disconnected the session licensing protocol windows server 2008 including Microsoft sites.So unless you have an EXACT match ofsolution to problem DO NOT tell me toTRY this or that in
The Remote Computer Disconnected Session Licensing Protocol Windows 7
any article as I have probably already read it or tried it. OK onto the issue. Brand new 2008 R2 SP1 standard Dell server. All updates applied. Joined as a stand alone server to domain. Remote
Change The Terminal Server Licensing Mode From Per Device To Per User
desktop role installed. License server role installed. License server activated. 10 Per User RD (open License) Cals installed. Remote Desk Host Diagnostics gives clean bill of health. No other roles etc. installed. This is strictly a TS server. Workstations are Wyse thin clients running Windows 7 Embedded. They can see all allowed resources on domain. they can get to the internet as well. network connectivityand navigation confirmed. So.... When I start up RDP mslicensing registry key missing client on said terminals I get error of:The remote computer disconnected the session becase of an error in the licensing protocol. Remeber this is a Windows 7 embedded. hacks to registry or file copy from other OSes do not apply. And yes I checked with Wyse support. other Misc data: No firewall activated on server using the administrator account to attempt logon as it is already included in group. (Should not matter as it is a LICENSING PROTOCOL error anyway) It is part of a 2003 domain. No I have not edited GP on 2003 system. Yes the event log has been reviewed. I see NO entries for this issue. IDEAS????? Thursday, May 19, 2011 6:39 PM Reply | Quote Answers 1 Sign in to vote Issue Resolved. With Windows 7 the security settings for a regular user are severe. What would have worked for Vista and previous will not work with Windows 7. To get this to work you must log in as the administrator on Wyse terminal. (hold down shift key when selecting logoff.) choose Administrator on logon screen. Password (default) Wyse#123 (case sensitive). Disable write protect. (There is a shortcut for it on the desktop.) System will restart automatically.Logon to Wyse terminal administrator again. Setup your RDP session fo
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
The Remote Session Was Disconnected Because There Are No Remote
“there are no terminal server client access licenses available for this computerâ€. Well, the remote session was disconnected because license store creation failed with access denied that's easy, I walked her through and successfully deleted the MSLicensing registry key on her Windows Vista computer, and mslicensing key 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 https://social.technet.microsoft.com/Forums/windowsserver/en-US/d64d00c4-c87b-4af6-83b5-54daf2c82938/remote-desktop-licensing-protocol-error?forum=winserverTS 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 http://www.kjctech.net/the-remote-computer-disconnected-the-session-because-of-an-error/ 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 persistent (9
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 ads with http://serverfault.com/questions/54893/remote-desktop-to-win-2008-error-in-license-protocol 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 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 to a the remote 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 real issue here is the remote computer 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 answer answered Aug 17 '09 at 9:20 Mark Henders