Because Of A Protocol Error Code 0x1204
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
Because Of A Protocol Error Detected At The Client 0x1204
the client Windows 7 IT Pro > Windows 7 Networking Question 0 code 0x1204 rdp Sign in to vote I'm suddenly receiving a critical remote desktop error at the client stating the following
Protocol Error Detected At The Client Code 0x1104
(it differs from time to time) "Because of an error in data encryption, this session will end. Please try connecting to the remote computer again." "Because of a protocol because of a protocol error detected at the client (code 0x2104) 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 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 because of an error in data encryption this session will end remote desktop windows 7 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 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 (troubl
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
Protocol Error Detected At The Client 0x1104
fix the issue: 1. In your RDP client settings, remove all checkmarks from change security layer of the rdp tcp session to rdp security layer Experience tab (see screenshot below). This seems to work for most people: 2. If you're running your RDP server on
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
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 be using the https://social.technet.microsoft.com/Forums/windows/en-US/68910414-0271-4da8-bd92-35908370aea5/remote-desktop-encryption-error-at-the-client?forum=w7itpronetworking 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 and run tcpview.exe. Search for 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/ 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 2003 terminal server and get this same error from my w
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for https://www.experts-exchange.com/questions/27814183/RDP-Session.html Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > RDP Session Want to Advertise Here? Solved RDP Session protocol error Posted on 2012-08-02 Windows Server 2003 1 Verified Solution 3 Comments 1,915 Views Last Modified: 2012-10-12 Dear All, Through Thin-client we are connecting the RDP session for Win2003 Server getting an Error message. "Remote Desktop Error Code 0x1204 - Because of a protocol error detected at the client, this session will be disconnected. because of a Please try connecting to the remote computer again." RDP session is connecting through Terminal License Server, almost all the Thin-client, Winxp and Win7 OS are able to connect through RDP. Only 5 Thin-clients are unable to establish the RDP connection. Let me know if you require any more details. Thanks and Regards, Venkatesha.A 0 Question by:axonnet Facebook Twitter LinkedIn Google LVL 4 Best Solution byK-H Copy mstscax.dll and mstsc.exe from another computer and replace it. C:\Windows\System32\ & C:\Windows\System32\en-US reboot pc and it should work. Regards Go to Solution 3 Comments LVL 19 Overall: Level 19 Windows Server 2003 6 Message Expert Comment by:1stITMAN2012-08-02 Are these HP thin Clients ? If so upgarde the BIOS on them. 0 LVL 4 Overall: Level 4 Windows Server 2003 1 Message Accepted Solution by:K-H2012-08-02 Copy mstscax.dll and mstsc.exe from another computer and replace it. C:\Windows\System32\ & C:\Windows\System32\en-US reboot pc and it should work. Regards 0 LVL 4 Over