Protocol Error 0x1104 Windows 7
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My because of a protocol error detected at the client (code 0x1104) this session will be disconnected Forums Answered by: Remote Desktop Encryption error at the client because of a protocol error this session will be disconnected windows 7 Windows 7 IT Pro > Windows 7 Networking Question 0 Sign in to vote I'm suddenly because of a protocol error detected at the client (code 0x2104) receiving a critical remote desktop error at the client stating the following (it differs from time to time) "Because of an error in data encryption, because of a protocol error the client could not connect to the remote computer this session will end. Please try connecting to the remote computer again." "Because of a protocol error detected at the client (code 0x1204), this session will be disconnected. Please try connecting to the remote computer again." I've been running on the same windows 7 64 bit build on a Dell M4500
Because Of A Protocol Error (code 0x112f)
for well over a year in RDP sessions daily over VPN's without issue. Suddenly one day last week i began receiving this error. I can, onoccasion, connect to local LAN RDP's without the error immediately but have experienced the error even on LAN sessions after 3-5 minutes of use. Sometimes on a LAN it will go much longer. Now, for remote sessions, i cannot authenticate at all. I typically get to the login screen, enter my credentials, then immediately the error pops up and drops the connection. Every time. I've tried this to multiple different WAN's so i know it's not at the server level. I also know it's not on my LAN as other PCs on the LAN connect fine without this error so it's local to this PC. After hours of diagnosing and reading articles i decided to just rebuild from the ground up, fresh install of windows, applied
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:
Because Of A Protocol Error This Session Will Be Disconnected Please Try Connecting Again
1. In your RDP client settings, remove all checkmarks from Experience tab (see screenshot because of a protocol error (code 0x112d) below). This seems to work for most people: 2. If you're running your RDP server on a non-standard port (such as change security layer of the rdp-tcp session to "rdp security layer" 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 out what else may be using the port assigned to RDP (i.e. 443 https://social.technet.microsoft.com/Forums/windows/en-US/68910414-0271-4da8-bd92-35908370aea5/remote-desktop-encryption-error-at-the-client?forum=w7itpronetworking 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 - 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. 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/ 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 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 re
a Question Ask 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 https://www.experts-exchange.com/questions/26806932/Remote-Desktop-Protocol-error-code-0x1104.html Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Experts Exchange > Questions > Remote Desktop Protocol error - code 0x1104 Want to Advertise Here? Solved Remote Desktop Protocol error - code 0x1104 Posted on 2011-02-08 Windows 7 Windows XP Network Operations 1 Verified Solution 9 Comments 7,905 Views Last Modified: 2012-05-11 I protocol error use to be able to connect to my home desktop using my public 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. because of a 0 Question by:rpmccly Facebook Twitter LinkedIn Google LVL 7 Best Solution byDk_guru Start at the simplest point; Make 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 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 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 ha