Anyway, I'm not absolutely convinced this is the only solution, even if it is functional; hence the 'good' versus 'great' rating. 0 LVL 59 Overall: Level 59 Windows Server 2008 Any suggestions are greatly appreciated. 0 Question by:mbresit Facebook Twitter LinkedIn Google LVL 59 Best Solution byDarius Ghassem Have you tried these? OY!!!! That was it. this contact form
If the problem still persists, let me know so that I can send the exact procedure. You will need to find one that fits your scenario but there is not a place on the server to say fix this. narayanan February 4, 2010 at 11:29 am hi, am also facing similar problem. asked 4 years ago viewed 16301 times active 10 months ago Blog Stack Overflow Podcast #92 - The Guerilla Guide to Interviewing Related 2Certificate for Terminal Services authentication on Windows Vista7Can http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/remote-desktop-connection-error-message-the-remote/cc914f39-3d8e-4671-b569-b1ba5d68b380
If you try the same thing on Windows Vista or Windows 7, when you try to reconnect to the server you get this message: The remote computer disconnected the session because Giving a lower grade on a solution that worked but didn't meet your expectation of a solution that currently is not feasible because of limitation of the OS and how it Edit: I didnt read your question properly, as mrdenny said you dont need to install the Terminal Services role in order to remotely access the server for administration. If running Windows 7 or Vista, you must right click on the Remote Desktop Connection shortcut and choose “Run as Administrator” b.
Hot Network Questions Can One GFCI Serve Several Outlets Problem of display in tikz How does a migratory species advance past the Stone Age? What causes this and how to avoid it? Recommended reading: Registry tweak to improve performance of Windows XP SHARE Facebook Twitter tweet Gautam RELATED ARTICLESMORE FROM AUTHOR How To's How to Remove Shortcut Virus from Pendrive How To's Recover Licensing Protocol Error Remote Desktop Windows Server 2008 Wole September 6, 2010 at 2:17 pm Thanks guys..copying MSLicensing registry key from a PC known to be working to the PC with the problemw saved the day.
I have also tried: mstsc -console without any luck. The key was deleted, I ran the RDP Client as an Administrator but was still given the same error. Robert January 5, 2011 at 1:24 am This all still begs the question of why doesn't Microsoft fix this problem??? http://www.techbuzz.in/how-to-fix-the-remote-computer-disconnected-the-session-because-of-an-error-in-the-licensing-protocol.php You receive 'The remote computer disconnected the session because of an error in licensing protocol' when you attempt to connect to a remote computer using Remote Desktop on a Windows XP
And yes, Microsoft now has it's own all-in-one. The Remote Session Was Disconnected Because License Store Creation Failed With Access Denied Have tried both but in reverse order. Remote Desktop Connection - The remote computer disconnected the session because of an error in the licensing protocol. Generated Wed, 26 Oct 2016 23:28:10 GMT by s_wx1087 (squid/3.5.20) Home About Articles Blog Links WordPress Contact RSS Welcome to Networknet Blog!
Fire November 16, 2010 at 7:18 pm In Windows 7 it's really important that you start the remote desktop session after deleting the registry key "as Administrator". http://fbinotto.blogspot.com/2013/06/the-remote-computer-disconnected.html Since a moderator is now involved, as you'd made very clear, if they believe you should be awarded a 'great' rating in spite of my comments then I won't belabor the The Remote Computer Disconnected The Session Because Of An Error In The Licensing Protocol 2008 R2 Thanks for the fix! 🙂 Reply Buzz Grant says: January 31, 2010 at 6:19 pm Thank you!! The Remote Computer Disconnected Session Licensing Protocol Windows 7 Thanks. 0 Message Author Comment by:mbresit2012-10-08 I've requested that this question be closed as follows: Accepted answer: 0 points for mbresit's comment #a38473834 for the following reason: Wish there were
What's the point of Pauli's Exclusion Principle if time and space are continuous? weblink Name * Email * Website Comment Add Comment Notify me of followup comments via e-mail Sponsor Search Search for: Recent Posts PowerShell: Automate SSO configuration for SAP GUI August 12, 2016 Local, Remote, 1 server 1 workstation with cross over cable. Hi there! Change The Terminal Server Licensing Mode From Per Device To Per User
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 What should I tell them? Connect with top rated Experts 21 Experts available now in Live! navigate here Thanks!
I'm an administrative professional whose company has a less than qualified IT guy…he was going to remove my computer from the office to fix this! Remote Session Was Disconnected Because There Are No Even though you want something this does not mean that you are always going to get it that way. But surprisingly, she replied a few seconds later saying no, still didn't work.
This will allow the RDC client permission to rebuild the necessary registry keys. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Get 1:1 Help Now Advertise Here Enjoyed your answer? Mslicensing Registry Key Missing Could it be that the Terminal Server was restarted and in the process my laptop's ID was lost?
Thank you Thank you Thank you 🙂 Reply TheQuestor says: March 15, 2010 at 1:04 am You sir are a god. Did I mention that this problem was actually occurred on a Vista computer above? Delete the MSLicensing key a. his comment is here Log In or Register to post comments klimenta on Dec 19, 2008 I had the similar problem where the terminal server was behind the firewall and only RDP ports were open.
Gautam H N May 4, 2009 at 7:36 pm @ Softwaresnhard - I don't see a reason why this would not work .. I have 125 servers in the fileld around 8000 workstations… and all have this problem. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys. The only solution was to RDP to a Terminal Server on the same side of the firewall, log off and get a temporary CAL.