Rds Remote Control Protocol Error
Contents |
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 because of a protocol error this session will be disconnected. please try connecting to the remote Us Learn more about Stack Overflow the company Business Learn more about hiring
Remote Desktop Protocol Error 0x112f
developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a
Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected
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
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
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 because of a protocol error this session will be disconnected windows 10 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|
joe0 ⋅ 4 Comments Following is a solution for RDP error: Because of a protocol error detected at the client code 0x1104 this session will be disconnected. Two ways to fix the issue: 1. In your RDP client settings, remove all checkmarks from Experience tab (see screenshot because of a protocol error this session will be disconnected windows 8 below). This seems to work for most people: 2. If you're running your RDP server on a protocol error remote desktop connection non-standard port (such as port 443-https), then it's possible some other app is fighting over the very same port. In that case, you'll need to find because of a protocol error this session will be disconnected server 2008 r2 out what else may be using the port assigned to RDP (i.e. 443 in my example) on your server. To do so, following steps will help you determine this: - Open a command prompt window. From Start / Run enter: cmd - http://serverfault.com/questions/200700/remote-desktop-session-ends-abruptly-with-a-protocol-error From the command prompt enter: netstat -ano 1 netstat -ano - Look for PID which indicates usage of the port 443: - Mark down PID, then download Tcpview and run tcpview.exe. Search for PID you've found by using command line netstat call. You'll find what app is taking over your RDP port. In my case, I could see that Skype is trying to run its service on port 443: - Solution in this case would be to completely close out of Skype. Or simply Kill/Uninstall http://www.joe0.com/2013/08/23/solution-for-rdp-error-because-of-a-protocol-error-detected-at-the-client-code-0x1104-this-session-will-be-disconnected/ or temporarily disable the Skype. While in tcpview, you may as well do so: Let me know if this helped. Comments comments Posted in: English Blog 4 Thoughts on “Solution for RDP error: Because of a protocol error detected at the client code 0x1104 this session will be disconnected” William J Lasiewicz on April 6, 2015 at 8:30 pm said: I tried all these things and finally I called someone in the office and had them power down my machine and bring it back up. This worked. Doing this will save you quite a bit of time. Reply↓ Arg on June 20, 2015 at 7:26 am said: Nope, nothing works. Wanna blow my brains out. Reply↓ Doug Symes on April 18, 2016 at 7:51 pm said: did you ever find the answer to this? I'm supporting an old 2003 terminal server and get this same error from my win7 client. Reply↓ inexpensive on June 2, 2016 at 3:16 pm said: ZW Reply↓ Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Post Navigation ← Previous Post Next Post → Search for: About Me Profile: Categories English Blog (248) Slovak Blog (46) Links 1. FB Comments Code Learning Videos ETX.ca Jozef's Tools Mortgage Calculator Extra Payments Online Documentaries Recipes of your dreams Siri for Android SpeedX Fan Site August 2013 M T W T F S S « Mar Sep » 1234 567891011 12131415161718 19202122232425 262728293031 Archives October 2016 September
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.