Protocol Error Client Code 0x1104
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 in to vote because of a protocol error the client could not connect to the remote computer I'm suddenly receiving a critical remote desktop error at the client stating the following (it rdp because of a protocol error this session will be disconnected differs from time to time) "Because of an error in data encryption, this session will end. Please try connecting to the remote because of a protocol error (code 0x112d) 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 https://support.software.dell.com/vworkspace/kb/85618 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 cannot authenticate at all. I typically get to https://social.technet.microsoft.com/Forums/windows/en-US/68910414-0271-4da8-bd92-35908370aea5/remote-desktop-encryption-error-at-the-client?forum=w7itpronetworking 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 2003, 2008, WIN7 or even XP remote desktop sessions Any ideas? I know, it's a
When attempting to access a remote computer using RDC, you may receive this message: "Because of a protocol error, detected at the client http://www.tomshardware.com/forum/145137-45-because-protocol-error-detected-client-code (code 0x1104) this session will be disconnected. Please try connecting to the remote computer again" Case 1: The terminal server is running an protocol error 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. because of a The remote client may receive this error when the Remote host IP changes. Case 4: I had this problem when i moved a server from a location to another. My 2003 server has got two NIC and i used one for the first location and the other for the second location. When i tried to connect with RDP to this server i found this problem. Looking for a solution in Terminal Services Configuration, I've founded it by authorizing the second Nic to be used for RDP. Case 5: Some software may changes the port #. Please check this link: Cant access TS with error code 0x1104 Post your questions, comments, feedbacks and suggestions Contact a consultant Related Topics This web is provided "AS IS" with no warranties. Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.