Rdp Because Of A Protocol Error Detected At The Client
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: Remote Desktop Encryption error at the client Windows 7 IT Pro > Windows 7 Networking Question 0 Sign
Because Of A Protocol Error Detected At The Client (code 0x2104)
in to vote I'm suddenly receiving a critical remote desktop error at the client change security layer of the rdp-tcp session to "rdp security layer" stating the following (it differs from time to time) "Because of an error in data encryption, this session will end. Please try
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
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 because of a protocol error detected at the client 1204 windows 7 64 bit build on a Dell M4500 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 remote desktop connection because of a protocol error this session will be disconnected 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 all service packs, updates and installed my VPN client and attempted the connection -- same error. I even used a brand new HDD (SSD) as i was wanting to upgrade it anyway. Now i recognize that i should have tried the connection before all other patches were installed (troubleshooting 101, sorry) but trying to avoid a 3rd install and hoping for assistance. I typically disable system restore so rolling back isn't an option. At this point i believe it's hardware related or an update causing the problem. It's also worthy to note that I've updated NIC and WLAN drivers, disabled TOL, and tried the connections over both connections -- same problem. I'm almost certain it's a client problem. I receive the error trying to connection to server
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: 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/ 1. In your RDP client settings, remove all checkmarks from Experience tab (see screenshot below). This seems to work for most people: 2. If you're running your RDP server on a non-standard port (such as http://serverfault.com/questions/510450/issue-connecting-over-rdp-when-on-windows-vpn 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 protocol error 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. because of a 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 reply
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 Issue connecting over RDP when on Windows VPN up vote 1 down vote favorite I have an issue that just began today and not sure what the cause is (I've been able to successfully connect this way for several years). On my Windows 7 box, I have a VPN set up in Windows. Today I was on the VPN and logged into an RDP session with no problem. I disconnected from the RDP session and the VPN. A few minutes later, I got back on the VPN, and when attempting several times to connect to the server over RDP again, I got several error messages: Because of a protocol error this session will be disconnected Because of a protocol error detected at the client (code 0x1104) Because of a protocol error detected at the client this session will be disconnected When attempting to browse a website in Chrome while connected to the VPN, no stylesheets would load. Google Drive lost connectivity, though Dropbox did not. Firefox displayed the following message: The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. I am also seeing SSL Protocol errors in Firefox, and other errors when secure (port 443) requests are made. Disconnecting from the VPN made browsing normally possible again and Google Drive came back. I have another Windows VPN which I connected to - same issues. The only thing I can think of is I earlier added a Windows Firewall rule to open ports 53, 88, 138,137,139, 389, 445, 636. I deleted the rule, rebooted, and even turned off the firewall and disabled Microsoft Security Essentials but the issue did not go away. One other thing - for servers where I do not have to be on a VPN, I can remote desktop fine. I'