remote computer disconnected session because error licensing protocol xp Higley Arizona

On-Site & Remote Computer services / Repair

Address Gold Canyon, AZ 85118
Phone (480) 266-0550
Website Link
Hours

remote computer disconnected session because error licensing protocol xp Higley, Arizona

Windows XP – simply run Remote Desktop Connection 5. Now connects fine. Gautam February 4, 2010 at 12:10 pm @Narayanan - Whats the environment you are working in ? Log out of administrator on Wyse terminal.

We have 4 other TS users, neither of whom are having any problem connecting. "The remote computer disconnected the session because of an error in the licensing protocol Please try connecting The software should regenerate the keys and you will see the login screen Hassan December 20, 2010 at 6:00 pm Hi, I hade the same problem: This solv my problem. Disable write protect. (There is a shortcut for it on the desktop.) System will restart automatically.Logon to Wyse terminal administrator again. If in case you still face problems, especially because of registry key, the you can overwrite the new registry setting with your old one, since you would have taken a backup.

Could it be that the Terminal Server was restarted and in the process my laptop's ID was lost? Art January 12, 2011 at 1:45 am This worked like a champ. Onyour thin clients, do you not have the ability to run the Remote Desktop Client as an Administrator? Both are running Windows XP pro and both have up to date SP's.

Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Join and Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Log off and go back into Administrator onwyse terminal. 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.

Based on everything that you are seeing this (unique issue) would be the likely culprit. Try to put site in trusted sites as well 0 Message Author Comment by:mbresit2012-10-08 Thanks. This is strictly a TS server. Aug 28, 2006 Jerold Schulman | Windows IT Pro EMAIL Tweet Comments 2 Advertisement When you attempt to connect to a remote computer using Remote Desktop on a Windows XP Professional

My problem is I could not delete that registry file under MSLicensing and I have 2 folders under MSLicensing, they are hardwareID & Store. When you attempt to connect to a Remote Access Server, you receive 'The Local Security Authority cannot be contacted (Error 0x80090304)' or 'Error 0x80090022: Providers could not perform the action since But this hasn't worked. Q.

Type FixRDMSL.bat, or the fully qualified file name, and press Enter. 3. In the majority of cases it is not necessary to delete the MSLicensing key. -TP Proposed as answer by Amy Wang_Microsoft contingent staff, Moderator Monday, November 09, 2015 9:43 AM Marked Your Windows XP and Windows 2000 clients receive 'The remote session was disconnected because the local computer client access license could not be upgraded or renewed' when they attempt to connect To resolve this behavior, I have scripted FixRDMSL.bat, which contains: @echo off setlocal call :Quiet>nul 2>&1 set key=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing for /f "Tokens=*" %%a in ('REG QUERY %key%^|find /i "%key%\"') do ( @echo

Robert January 5, 2011 at 1:24 am This all still begs the question of why doesn't Microsoft fix this problem??? The solution is correct. 0 Message Author Comment by:mbresit2012-10-08 I gave you your points, so what's the issue? Have you connected to the registry on one of the thin clients and checked permissions on the MSLicensing key? been spending many hours on the server-side tring to fix the problem.

and both we access thru remote desktop, while one server we were able to connect thru remote desktop, another server we getting that error. Verify that RDP session to your Terminal server still works. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? if you can Telnet successfully, then you will probably find an issue at the server itself.

Joined as a stand alone server to domain. Log off and go back into Administrator onwyse terminal. Re-enable write protect. What would have worked for Vista and previous will not work with Windows 7.

Looking to get things done in web development? This may or may not the case, but I simply don't know that. Delayed effects after player's death Should non-native speakers get extra time to compose exam answers? Were you able to right-click on mstsc.exe and choose Run as Administrator, then connect to the server?

However, I thank you for your contribution as it has provided a useful service. I had thanked you twice for your answer in that same post. Best Chass January 14, 2010 at 12:41 am I'm running Vista Home trying to fix the same problem with a users computer. So....

CLOSE News Mobile Applications Iphone Windows Phone Gadgets Design Photography Reviews More Apple Android Windows Phone Iphone Thursday, October 27, 2016 Sign in / Join LOG IN Welcome! This worked for Windows 7. All goes well for a very long time. IDEAS?????

Restarted Thin. Matt October 29, 2009 at 9:32 pm Got same problem. please help…. If there isn't a server-side solution (or avoidance mechanism), there should be, given the only variable in this equation is the server.

I see NO entries for this issue. We have home users which are experiencing this issue in addition to those which we have direct control over. Repeat the process of RDP setup. Actually we have hosted 2 server in data centre.

When you attempt to connect to a Remote Access Server, you receive 'The Local Security Authority cannot be contacted (Error 0x80090304)' or 'Error 0x80090022: Providers could not perform the action since Anyway, this worked. Covered by US Patent. or Delete the MSLisencing "HKLM\Software\microsoft\Mslicensing"key from the workstation and reboot it.

it will generate anew MsLisencing key inside Registry "HKLM\Software\microsoft\Mslicensing" it would work for next 90 days until you wouldpull up the RDP for the next time. Any suggestions are greatly appreciated. 0 Question by:mbresit Facebook Twitter LinkedIn Google LVL 59 Best Solution byDarius Ghassem Have you tried these? This is pirated from another website. Rebooting will create new Keys under HardwareID and Store and this will fix your problems. 5> If you had renamed the keys and subkeys instead of deleting them, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

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 RDP from Full OS XP clients and windows 7 do not have issues. Cheers, ben February 4, 2011 at 4:47 am I just wanted to make sure when you said "delete the MSLicensing key", you meant the whole folder or just the registry file JoinAFCOMfor the best data centerinsights.