Mstsc Protocol Error 0x1104
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 client settings, remove all checkmarks from Experience tab because of a protocol error this session will be disconnected windows 7 (see screenshot below). This seems to work for most people: 2. If you're running your RDP because of a protocol error (code 0x112f) server on a 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, because of a protocol error this session will be disconnected please try connecting again 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 steps will help you determine this: - Open a command prompt window. From Start because of a protocol error (code 0x112d) / 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 could see that Skype is trying to run its service on port 443: - Solution in this case would be to completely
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
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 Me Profile: Categories English Blog (247) Slovak Blog (46) Links 1. FB Comments ETX.ca Jozef's Tools Mortgage Calculator Extra Payments Online Documentaries Siri for Android SpeedX Fan Site August 2013 M T W T F S S « Mar Sep » 1234 567891011
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery 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
Because Of A Protocol Error Detected At The Client (code 0x2104)
Server > Windows Server General Forum Question 0 Sign in to vote change security layer of the rdp-tcp session to "rdp security layer" Hi, Have a Windows Server 2003 SP2 with latest patches and updates. The remote access to the server because of a protocol error this session will be disconnected server 2008 r2 no longer works. I noticed that the PortNumber value of the HKLM\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp had been changed from 3389 to 3399. I changed it back to 3389 and rebooted the machine. 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/ It worked for a day os so then stopped working. I then noticed that the port number had 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 https://social.technet.microsoft.com/Forums/office/en-US/9df2f4bd-0177-4cbb-ad02-96561d6b24e4/cannot-connect-remote-desktop-code-0x1104-to-windows-server-2003?forum=winservergen 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 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
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit https://www.experts-exchange.com/questions/26806932/Remote-Desktop-Protocol-error-code-0x1104.html Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Remote Desktop Protocol error - code 0x1104 Want to Advertise Here? Solved Remote Desktop Protocol http://www.pronetworks.org/forums/remote-desktop-connection-error-0x1104-t70131.html error - code 0x1104 Posted on 2011-02-08 Windows 7 Windows XP Network Operations 1 Verified Solution 9 Comments 7,889 Views Last Modified: 2012-05-11 I use to be able to connect to my home desktop using my public protocol error ip but now I get a protocol error code 0x1104. I can't even do remote desktop on my internal network using my local ip addresses within my network. Anyone know what it is? I am running on a Windows 7 x64. As far as I know, nothing has changed from my router or desktop since it happened. 0 Question by:rpmccly Facebook Twitter LinkedIn Google LVL 7 Best Solution byDk_guru Start at the simplest point; Make because of a sure that your remote settings have not been changed. (right click on my computer, select properties, select remote settings - make sure that RDP is enabled and allowed. Go to Solution 9 Comments LVL 3 Overall: Level 3 Message Expert Comment by:rdmustang2011-02-08 Did you add a 2nd NIC to the computer? If so you'll need to configure RDP to listen on the 2nd NIC. Also, have you tried telnet'ing to 3389 on the remote computer? 0 LVL 24 Overall: Level 24 Network Operations 7 Windows 7 5 Windows XP 3 Message Active 4 days ago Expert Comment by:diverseit2011-02-08 Are you using the updated RDP client? In your network try using the computer name instead of the IP? Does that work? I'm assuming the internal IPs are static or reserved, correct? Try http://support.microsoft.com/kb/898060 0 LVL 24 Overall: Level 24 Network Operations 7 Windows 7 5 Windows XP 3 Message Active 4 days ago Expert Comment by:diverseit2011-02-08 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 as Remote Host with DHCP setup
Support Guides & Tutorials Tech Chit Chat Alpha & Beta Software CSS3 & HTML5 Hardware Customizing Security & Virus News Tech News Security News Software News Advertise Connect Facebook Twitter Google Plus Folding @ Home Contact Us Technology, Support, and News Forum Board index SUPPORT FORUMS General Windows Support Search Advanced search FAQ Login Username: Password: Log me on automatically each visit http://www.pronetworks.org/forums/ucp.php?mode=register&sid=1ecc656b1c5dff9611e2bff347ea3d85 I forgot my password View unanswered postsView active topics Remote Desktop Connection Error 0x1104 Post a reply 2 posts • Page 1 of 1 Remote Desktop Connection Error 0x1104 by steve_iss » Sun Feb 05, 2006 4:05 am Does anyone know what the error message "Because of a protocol error detected at the client (code 0x1104), this session will be disconnected." means? That and how is it fixed? Tons of thanks to who ever can. Steve steve_iss Profile Posts: 13Joined: Sun Feb 05, 2006 4:00 amLocation: Omaha, NE Top by jbullard » Sun Feb 05, 2006 4:21 am Well, unfortunately this error can mean many things. Anywhere from a faulty router (if using one) to a trojan. Some simple things that you can check is to make sure that the computer you are trying to connect to does not have a program that is using the same port that you are trying to connect through. Also, clear your dns cache, and possibly reboot both lan connections. Also, I found this online and hopefully it will help. This error indicates that RDP is not available to use TCP port 3389l. Occasionally, RPC provides 3389 to another service and this does not allow RDP to function. RPC can be isolated and confirmed if you stop the MSExchangeSA service.To keep this from happening in the future add the following using regedt32:(of course, backup the registry keys before making these changes).Add the following key if not present: Highlight the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc From Edit menu select "Add Key..."