Error 4356 Rdp
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 rdp protocol error 0x1104 Networking Question 0 Sign in to vote I'm suddenly receiving a critical remote because of an error in data encryption this session will end remote desktop windows 7 desktop error at the client stating the following (it differs from time to time) "Because of an error in data encryption, change security layer of the rdp-tcp session to "rdp security layer 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 because of a protocol error detected at the client 0x2104 computer again." I've been running on the same 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
Protocol Error Detected At The Client 0x1104
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 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,
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
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
ways to fix the issue: 1. In your RDP client settings, remove all because of a protocol error this session will be disconnected windows 8 checkmarks from Experience tab (see screenshot below). This seems to work for most people: 2. If you're running your RDP because of a protocol error this session will be disconnected windows 7 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, you'll need to find out what else may https://social.technet.microsoft.com/Forums/windows/en-US/68910414-0271-4da8-bd92-35908370aea5/remote-desktop-encryption-error-at-the-client?forum=w7itpronetworking 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 - 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 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/ 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 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 20
topic … Fix Rdp Error 4356 - Repair Windows – Easy Way to Fix Remote Desktop Error protocol error 4356 – How to repair Remote Desktop Error 4356 … RDP connect issue: Protocol Error 3334 – JIRA,mRemoteNG View topic … Fix Rdp Error 4356 - Repair Windows – Easy because of a Way to Fix Remote Desktop Error 4356 – How to repair Remote Desktop Error 4356 … RDP connect issue: Protocol Error 3334 – JIRA,mRemoteNG View topic … Fix Rdp Error 4356 - Repair Windows – Easy Way to Fix Remote Desktop Error 4356 – How to repair Remote Desktop Error 4356 … RDP connect issue: Protocol Error 3334 – JIRA,mRemoteNG View topic … Bookmark the permalink. Post navigation ← Snapdrive Error Access Is Denied Runtime Error Do You Wish To Debug → Search Striker WordPress Theme Powered By WordPress
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 Windows Remote Desktop protocol error up vote 1 down vote favorite So, related to this question, I am now also trying to integrate Windows Remote Desktop for certain other boxes that my app's users will have to remote into. I have a known good remote box and can connect through the user interface, but when I try to connect from the command line I get a message: "Because of a protocol error detected at the client (code 0x1104), this session will be disconnected. Please try connecting to the remote computer again." I looked at the command-line switches, and there doesn't seem to be anything I can do other than specify a config file, which doesn't help as I don't know what setting is making it connect. Help? windows remote-desktop share|improve this question asked Jan 21 '11 at 0:01 KeithS 130212 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted Never mind. I was told by the admin that I should use a different port than the default for RDP connections; turns out that port is used by VNC Server and thus the error (VNC and RDP don't speak the same language). I tried it from the command line without a port and it works fine, also works fine with the default 3389. share|improve this answer answered Jan 21 '11 at 0:07 KeithS 130212 add a comment| up vote 0 down vote Looks like that some o