0x1104 Error
Contents |
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
Protocol Error 0x1104 Remote Desktop
client settings, remove all checkmarks from Experience tab (see screenshot below). This seems to work protocol error code 0x1104 for most people: 2. If you're running your RDP server on a non-standard port (such as port 443-https), then it's possible some other rdp protocol error 0x1104 app is fighting over the very same port. In that case, you'll need to find out what else may be using the port assigned to RDP (i.e. 443 in my example) on your server. To do so, following
Because Of A Protocol Error Code 0x1104
steps will help you determine this: - Open a command prompt window. From Start / Run enter: cmd - 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
Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected
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 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
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Cannot connect remote desktop (code 0x1104) to Windows Server 2003 Windows Server > Windows Server General Forum Question 0 because of a protocol error this session will be disconnected windows 7 Sign in to vote Hi, Have a Windows Server 2003 SP2 with latest patches
Because Of A Protocol Error Detected At The Client (code 0x2104)
and updates. The remote access to the server no longer works. I noticed that the PortNumber value of the HKLM\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp because of a protocol error (code 0x112f) had been changed from 3389 to 3399. I changed it back to 3389 and rebooted the machine. It worked for a day os so then stopped working. I then noticed that the port number had 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/ been changed to 2288. I changed it back to 3389 and even though this value remains unchanged, a remote connection no longer works and I get a messge (Beacuse od protocol error detected on the remote client (code 0x1104), this session was disconnected. (Roughly ttranslated from French). Have the same error from different PCs on the LAN or via a VPN connection. If I do a "telnet servername 3389" I https://social.technet.microsoft.com/Forums/en-US/9df2f4bd-0177-4cbb-ad02-96561d6b24e4/cannot-connect-remote-desktop-code-0x1104-to-windows-server-2003?forum=winservergen get a message [hieroglyphics.. http://www.youngzsoft.com/cn/. A "netstat -no" indicates that the server is connected to 117.26.176.35, 117.26.180.162 and 120.40.251.213 via different ports. I suspect there is trojan installed but how do I go about detecting it and removing it. An antivirus scan did not detect anything. Moved by Roxana PANAITMicrosoft employee Tuesday, February 15, 2011 4:54 PM (From:Windows Server 2003 (et versions anterieures: Windows Server 2000, Windows NT Server)) Saturday, February 12, 2011 5:05 PM Reply | Quote Answers 0 Sign in to vote Hi, Here are some other reasons that may apply: Case 1: The terminal server is running an application that using the same port as the TS. Case 2: The server comes with two NICs and each of them has default gateway. That messes the routing table. No computer should have two default gates. Case 3: The client has XP\Win 7 as Remote Host with DHCP setup. The remote client may receive this error when the Remote host IP changes. Case 4: I had this problem when I moved a server from a location to another. My 2003 server has got two NIC and I used one for the first location and the other for the second location. When I tried to connect with RDP
When attempting to access a remote computer using RDC, you may receive this message: "Because of a protocol error, detected at the client http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html (code 0x1104) this session will be disconnected. Please try connecting to the remote computer again" Case 1: The terminal server is running an protocol error application that using the same port as the TS. Case 2: The server comes with two NICs and each of them has default gateway. That messes the routing table. No computer should have two default gates. Case 3: The client has XP as Remote Host with DHCP setup. because of a The remote client may receive this error when the Remote host IP changes. Case 4: I had this problem when i moved a server from a location to another. My 2003 server has got two NIC and i used one for the first location and the other for the second location. When i tried to connect with RDP to this server i found this problem. Looking for a solution in Terminal Services Configuration, I've founded it by authorizing the second Nic to be used for RDP. Case 5: Some software may changes the port #. Please check this link: Cant access TS with error code 0x1104 Post your questions, comments, feedbacks and suggestions Contact a consultant Related Topics This web is provided "AS IS" with no warranties. Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.
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 (code 0x1104), this session will be disconnected. please try connecting to the remote computer again" pls help! Solution: The most common reason why this is happening is because you are 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. 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): 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 fixed. You are a hiro. Thanks thanks thanks...ReplyDeleteAnonymousJanuary 12, 2010 at 5:21 PMI'm trying to connect my Mandriva power pack 2010 with vista business it didn't work still the same problem with turning of my firewall (on Linux) and login as anyone still the same result.Do i have to open port 5900 on in my routerReplyDeleteAnonymousFebruary 22, 2010 at 6:49 PMI uncheck Both Theme and Persistent bitmap caching. Is working. Thanks!ReplyDeleteAnonymousFebruary 25, 20