Because Of Protocol Error Remote Desktop Connection
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: because of a protocol error this remote desktop connection because of a protocol error this session will be disconnected session will be disconnected. please try connecting to remote computer again Windows remote desktop connection because of a protocol error detected at the client 7 IT Pro > Windows 7 Miscellaneous Question 0 Sign in to vote Hi, When i remote desktop remote desktop connection because of a protocol error detected at the client (code 0x1104) to a terminal server from windows 7 RC and run terminal services manager and remote control a terminal server session (which i do quite a bit, as i am an
Remote Desktop Connection Protocol Error Windows 7
IT Administrator) it connects to the session for a split second but then disconnects and displays the following error: because of a protocol error this session will be disconnected. please try connecting to remote computer again It does this every time i try and connect to a terminal server session.... annoying much! Anyone had a similar problem or is this alreadya because of a protocol error this session will be disconnected windows 7 known problem, i have search the forum but could not find anything related. Please could anyone help. Thanks. Thursday, May 07, 2009 8:06 AM Reply | Quote Answers 0 Sign in to vote After three whole days of slamming my head in the car door, I have come to the conclusion that the problem is the mstscax.dll and mstsc.exe in the system 32 file and the other two files in the en-US or your language folder, that is the culprit, that is giving the unstable connection, reason being is that I switched that file with a known good working rdc in vista and it works flawlessly in windows 7, let me know if you need any help!! Marked as answer by Ronnie VernonModerator Sunday, May 10, 2009 2:49 PM Sunday, May 10, 2009 12:26 PM Reply | Quote All replies 0 Sign in to vote After three whole days of slamming my head in the car door, I have come to the conclusion that the problem is the mstscax.dll and mstsc.exe in the system 32 file and the oth
Problem: i had remote desktop up and running on a PC and then i got this: "because of a protocol error detected at the client because of a protocol error detected at the client (code 0x1104) this session will be disconnected (code 0x1104), this session will be disconnected. please try connecting to the
Because Of A Protocol Error This Session Will Be Disconnected Windows 8
remote computer again" pls help! Solution: The most common reason why this is happening is because you are
Because Of A Protocol Error (code 0x112f) The Remote Session Will Be Disconnected
using a custom VISUAL STYLE with your computer. Set the visual style back to LUNA on XP or CLASSIC and see if the error occurs again. Most likely it will not. https://social.technet.microsoft.com/Forums/windows/en-US/4523ce86-9a0b-4e6c-90d1-225ddda67ce5/because-of-a-protocol-error-this-session-will-be-disconnected-please-try-connecting-to-remote?forum=w7itprogeneral Not all visual styles produce this error, but if you want a custom visual style on the remote computer then you will have to find a compatible visual style that works with RDP via trial and error. Another solution would be to set the RDP client to NOT use the visual styles by unchecking the box that says THEMES (see pic below): http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html Posted by computerboom at 9:12 AM 43 comments: kenmFebruary 4, 2009 at 2:43 AMMany Thanks."the box that says THEMES"fixed the problem for me.ReplyDeleteAnonymousSeptember 7, 2009 at 8:00 PMthnks! mate...... it works... seems like the advanced theme on remote computer was the problem....and unchecking the theme N bitmap option made it workReplyDeleteAnonymousSeptember 8, 2009 at 5:38 AMThanks for the lead. As an update, I'm using Windows 7, and connecting back to an XP machine. The themes work, but it was the "Persistent bitmap caching" that was causing my issue.ReplyDeleteAnonymousOctober 6, 2009 at 10:05 AMExcelente!! Después de probar y probar, realicé la conexión con la opción Themes deshabilitada y adios problema.Muchas gracias!!ReplyDeleteAnonymousOctober 8, 2009 at 2:51 PMThanks for the solution. Unchecking the "Themes" in the "Experience" tab worked for me.ReplyDeleteAnonymousNovember 19, 2009 at 2:16 PMFinally a solution that actually works without registry edits and file replacements! Thank you!ReplyDeleteAnonymousDecember 18, 2009 at 4:41 AMfyi: in my case (with the latest RDP), unchecking 'Visual Styles' (as themes are now dubbed) didn't do the trick -- But: unchecking 'Persistent bitmap caching' did!ReplyDeleteAnonymousJanuary 12, 2010 at 11:50 AMThanks you guys. My porblem is
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 http://serverfault.com/questions/200700/remote-desktop-session-ends-abruptly-with-a-protocol-error Learn more about hiring developers or posting ads with 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 session ends abruptly with a “protocol error” up protocol error vote 4 down vote favorite Intermittently we get a problem where a remote desktop session will get disconnected with the error message “Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.” We are getting this with one server only which is running Windows Server 2008, connecting with Windows 7 clients. The session itself stays running, you just get disconnected, and you can try and reconnect. Sometimes you because of a get in for a while then it will kick you out. We are connecting from Windows 7 clients. We have tried connecting using Cord on a Mac and this works fine, so it's not like the session itself is corrupted. One problem is that there are some critical applications running under the session (I know, let's not discuss the idiocy of that), so we cannot reset the session in any way during the working day – so any diagnostics must have minimum impact. 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 stalking me Nov 11 '10 at 17:18 Yes - once the session is in this 'state', I can't connect from any Windows 7 client (I don't have Vista/XP to try). I can connect using Cord from Mac or some other open source product on CentOS. –Jon Nov 15 '10 at 8:55 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote I had the same issue and luckily I found the solution on the social.technet.microsoft.com forum: ... Change the RDP Compression setting on the server to "Balances memory and network bandwidth" (recommended) or "Optimized to use less memory" using Group Policy. share|improve this answer a