It still works for me. I'm wondering if it is one of the hotfixes/windows updates that was released that caused this. Please set mark as answer it. Twitter'da Takip Et! this contact form
Wednesday, October 21, 2009 3:09 PM Reply | Quote 0 Sign in to vote Errrr. Each blade hosting two 2008 Svr 64 hosts 1 Guest is a Terminal server with 44 paid up liscences. Tuesday, September 21, 2010 8:15 AM Reply | Quote 0 Sign in to vote I have downloaded the patch on Windows 7 x64 and it works. have they all been disconnected together? 1 Message Active 1 day ago Author Comment by:sglee2013-11-11 "if they do not run the app, do they stay connected?" ---> I noticed that
The hotfixhttp://support.microsoft.com/kb/2523307works great for windows 2008, but _not_ for 2008 R2. In detail: - a folder containing mstsc.exe (v.6.0.6001.18000) and mstscax.dll (v.6.0.6001.18266) - a subfolder "de-DE" (or "en-US"... It is sheer sloppiness! Montanageek Friday, November 11, 2011 10:00 PM Reply | Quote 1 Sign in to vote I am still having the issues as well.
Monday, May 02, 2011 7:29 PM Reply | Quote 0 Sign in to vote Hi, flyingkiwi, What you have seen is a bug we are aware of. The process we go through now is to use anything but Vista / Win 7 to RDP into our TS just to be able to assist users when shadowing them. Very very very very frustrating. Because Of A Protocol Error This Session Will Be Disconnected Windows 10 Have also tried to downgrade my RDP exe with no avail as win7 will not let me change the system32 folder HAS ANYONE MANAGED TO FIX THIS ISSUE YET?
Monday, August 25, 2008 Solution: because of a protocol error, this session will be disconnected. Remote Desktop Protocol Error 0x112f I'm also having the same issues as everyone else when RDP into 2003 TS Server from Windows 7 and using remote control via Terminal Server Manager. Thanks. I've had a paid support case open with Microsoft for months now...jumped through 100 hoops with no resolution.
Maybe not likely ... Because Of A Protocol Error This Session Will Be Disconnected Server 2008 R2 in my case the update that caused the issue is KB969084. If that end user is on a 2008 Terminal Server, then the session will disconnect as soon as I attempt to shadow, no matter what RDP version they are using when Daniel Lupu Edited by Daniel Lupu Friday, January 20, 2012 7:58 AM Friday, January 20, 2012 7:49 AM Reply | Quote 0 Sign in to vote This is still an issue?
Please try connecting to the remote computer again." (This is the same error I've been getting since making the switch to 7). but I am just thinking out loud. Because Of A Protocol Error This Session Will Be Disconnected Windows 7 Windows Server 2008 R2 1. Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected unchecking persistent bitmap caching worked on win7ReplyDeleteAnonymousFebruary 23, 2013 at 2:12 PMThank you very much.
This is really a pain when you have to do this all the time. http://supercgis.com/protocol-error/remote-desktop-protocol-error-session-disconnected.html Most of our sessions are initiated by Windows 7 (v7600) clients, and protocol errors are few. I did tested with some of my Wyse device it works fine As for Windows to Windows RDPing ... In the right pane, double-click on Set compression algorithm forRDPdata5. Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
Microsoft really needs to fix this ASAP. How to describe very tasty and probably unhealthy food Are there any ways to speed up blender compositor? Regards Andi I tried the above, and it still does not work. http://supercgis.com/protocol-error/remote-desktop-disconnected-due-to-protocol-error.html I asked the users to close the APP AND LOGOFF (not just click [x] on Remote Destkop title bar).
Thanks, Jon windows-server-2008 remote-desktop rdp share|improve this question asked Nov 11 '10 at 9:26 Jon 179236 Is this happening with all of your windows 7 client? –Not Kyle stop Because Of A Protocol Error This Session Will Be Disconnected Windows 8 Tuesday, February 21, 2012 8:13 PM Reply | Quote 0 Sign in to vote YEP. Thanks, ASA-HP Thursday, May 13, 2010 11:08 AM Reply | Quote 1 Sign in to vote Not sure if it applies here, but we were getting this error on Remote
This suggests the following: In hour heterogeneous environment, desktop sessions may be opened and reopened viaRDPby any number of administrators running different RDP clients, with different settings. I am wondering if un-checking check boxes for "Visual styles" and "Persistent bipmap caching" will resolve the problem ... Cheers.... Protocol Error Remote Desktop Connection I googled this message and found numerous solutions to try, so I decided to post the question because I can't possibly try/apply all of those remedies.
Wednesday, December 09, 2009 3:10 PM Reply | Quote 0 Sign in to vote indeed...the workaroud works but its a pain the .... Is working. Does any one know how to resolve it? his comment is here in my case the update that caused the issue is KB969084.
Error message Solution 1 Try to use Remote Desktop Manager 64bit. I did tested with some of my Wyse device it works fine As for Windows to Windows RDPing ...