License Protocol Error
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)
The Remote Computer Disconnected The Session Licensing Protocol Windows Server 2008
Question 0 Sign in to vote I have spent the last 4 hours looking mslicensing registry key missing for solution online including Microsoft sites.So unless you have an EXACT match ofsolution to problem DO NOT tell me toTRY this the remote computer disconnected session licensing protocol windows 7 or that in 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
Hkey_local_machine\software\microsoft\mslicensing
server to domain. Remote 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
Change The Terminal Server Licensing Mode From Per Device To Per User
confirmed. So.... When I start up RDP 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.) Sys
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 remote session was disconnected because license store creation failed with access denied crashing in iOS 10 Beta Gadgets Design Photography Cell Phone / Mobile Utilities Best Apps
No Terminal Server License Servers Available Citrix
for iPhone Photography Reviews Reviews Facebook versus Google Plus Reviews Battle of the tablets: Apple vs. Blackberry Reviews Epson WorkForce 635 All-In-One Printer, the remote session was disconnected 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 How to fix - 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... 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 5937 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 http://www.techbuzz.in/how-to-fix-the-remote-computer-disconnected-the-session-because-of-an-error-in-the-licensing-protocol.php 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 Start Menu -> Go to Run Command box -> Type regedit -> This opens the registry Editor. 2> Navigate to HKEY
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof of http://discussions.citrix.com/topic/315687-remote-desktop-causes-a-licensing-protocol-error-for-user-initiated-connections-to-rds-servers-but-not-to-non-rds-servers/ Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenApp XenApp 6.5 for Windows Server 2008 R2 http://fbinotto.blogspot.com/2013/01/remote-desktop-license-protocol-error.html Application Publishing Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Remote Desktop causes a licensing protocol error for user-initiated the remote connections to RDS servers, but not to non-RDS servers Started by J.R. van Doornik , 30 October 2012 - 08:56 AM Login to Reply 19 replies to this topic J.R. van Doornik Members #1 J.R. van Doornik 17 posts Posted 30 October 2012 - 08:56 AM Situation: A Citrix farm with a number of servers that are all started from the same the remote computer basic image through provisioning. This image contains Windows Server 2008 R2, fully patched, with XenApp 6.5 installed. Next to this is a separate Citrix farm that contains a test-environment for applications.Issue: User starts MSTSC (Remote Desktop) as an application on Citrix, and tries to connect to various other servers.- RDP shows a licensing protocol error on connecting to a Citrix server- RDP connects without any problems to a non-Citrix serverDetails:The remote user logs in through the internet and starts the remote desktop application which has been published for him. Upon starting the application however, and filling in the name of the server you want to connect to, the applications pops up a second 'logon screen' to provide apparently some passthrough credentials to the Remote Desktop application. When re-entering the data for the user, the connection seems to be made but ends in an error: 'The remote computer disconnected the session becase of an error in the licensing protocol.' This happens, regardless of the credentials I use here, even if I use Admin equivalent credentials.This error seems to point at problems with the registry, specifically the HKLM\Software