Protocol Error Disconnected
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 session will be disconnected. please try connecting
Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected
to remote computer again Windows 7 IT Pro > Windows 7 Miscellaneous Question because of a protocol error this session will be disconnected windows 7 0 Sign in to vote Hi, When i remote desktop to a terminal server from windows 7 RC and run because of a protocol error the client could not connect to the remote computer terminal services manager and remote control a terminal server session (which i do quite a bit, as i am an IT Administrator) it connects to the session for a split second but then
Because Of A Protocol Error (code 0x112d)
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 known problem, i have search the forum but could not find anything related. Please could anyone help. Thanks. Thursday,
Because Of A Protocol Error Code 0x112f The Remote Session Will Be Disconnected
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 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
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 17:45:03 GMT by s_wx1085 (squid/3.5.20)
Try to use Remote Desktop Manager 64bit. To do so, launch Remote Desktop Manager64.exe from the installation folder instead of Remote Desktop Manager.exe. protocol error Solution 2 Uncheck Bitmap Caching and Themes under the Experience tab in the properties of the RDP session. Uncheck Themes And Bitmap Caching Solution 3 because of a Close Remote Desktop Manager,rename default.rdp file in My Documents to default.old, restart Remote Desktop Manager and try to connect with RDP. Solutions 4 Login in to the target machine,by directly going to the console of that server or by any tool like VNC so that we can get access to that machine. After connecting: 1.Right Click on the Desktop2.Select the Properties3.There DropDown the Themes and select the theme other than the current one.4.Click on Apply, OK Now try to connect that machine remotely.
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 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 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 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