Protocol Error Detected 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 because of a protocol error detected at the client (code 0x1204) > Windows 7 Networking Question 0 Sign in to vote I'm suddenly receiving
Because Of A Protocol Error Detected At The Client (code 0x2104)
a critical remote desktop error at the client stating the following (it differs from time to time) "Because of an change security layer of the rdp-tcp session to "rdp security layer" error in data encryption, 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. because of a protocol error (code 0x112f) 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 can, onoccasion, connect to local LAN RDP's without the error immediately but have experienced the error even on
Because Of A Protocol Error Detected At The Client 1204
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 (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 causi
SonicWALL User Sorry, we are having issues processing your request. If you own the SonicWALL product requested please confirm that because of a protocol error the client could not connect to the remote computer you have registered your product at My SonicWALL . If you rdp because of a protocol error this session will be disconnected have already registered your product then please contact Customer Service directly for further assistance at customerservice@software.dell.com. Continue ×
Because Of A Protocol Error (code 0x112d)
Support Forms Under Maintenance Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for https://social.technet.microsoft.com/Forums/windows/en-US/68910414-0271-4da8-bd92-35908370aea5/remote-desktop-encryption-error-at-the-client?forum=w7itpronetworking the inconvenience. Continue Search Sign In Sign In Create Support Account Products ActiveRoles Boomi Change Auditor Foglight Identity Manager KACE Migration Manager Rapid Recovery Recovery Manager SharePlex SonicWALL Spotlight Statistica Toad View all Products Solutions Application & Data Integration Big Data Analytics Business Intelligence Cloud Management Data Protection Overview Backup and Recovery Deduplication and Compression Database Development https://support.software.dell.com/kb/sw12397 and Management Database Replication & Backup Endpoint Management Mobile Workforce Management Overview Desktop Virtualization Enterprise Mobility Management Endpoint Security Network Security Secure Remote Access Performance Monitoring Security Overview Email Security Endpoint Security Identity & Access Management Network Security Secure Remote Access Virtualization Management Microsoft Platform Management View all Solutions Solutions by Platform Active Directory Exchange Google GroupWise & NDS Hadoop Hyper-V Lotus Notes Skype for Business/Lync Office 365 Oracle SharePoint SQL Server VMware Trials Buy Support By Product Line Enterprise Reporter Foglight KACE Migration Manager Migrator NetVault One Identity Quick Connect Performance Analysis Recovery Manager Shareplex SonicWALL Spotlight SQL Navigator Toad All Products Contact Support Download Software Knowledge Base My Account My Products My Service Requests My Licenses My Groups My Profile Policies & Procedures Professional Services Technical Documentation Training & Certification User Forums Video Tutorials Support Home Communities Partners × Email Share your favorite Support content with a friend. Email To Email From Subject Information from Dell Software Support Message You might be interested in the following informati
Problem: i had remote desktop up and running on a PC and then i got this: "because of a protocol error detected at the client (code 0x1104), this session will be disconnected. please try connecting to http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html the remote computer again" pls help! Solution: The most common reason why this is happening is because you are using a custom VISUAL STYLE with your computer. Set the visual style back to LUNA on XP https://www.experts-exchange.com/questions/26806932/Remote-Desktop-Protocol-error-code-0x1104.html or CLASSIC and see if the error occurs again. Most likely it will not. Not all visual styles produce this error, but if you want a custom visual style on the remote computer then you will protocol error have to find a compatible visual style that works with RDP via trial and error. Another solution would be to set the RDP client to NOT use the visual styles by unchecking the box that says THEMES (see pic below): Posted by computerboom at 9:12 AM 43 comments: kenmFebruary 4, 2009 at 2:43 AMMany Thanks."the box that says THEMES"fixed the problem for me.ReplyDeleteAnonymousSeptember 7, 2009 at 8:00 PMthnks! mate...... it works... seems like because of a the advanced theme on remote computer was the problem....and unchecking the theme N bitmap option made it workReplyDeleteAnonymousSeptember 8, 2009 at 5:38 AMThanks for the lead. As an update, I'm using Windows 7, and connecting back to an XP machine. The themes work, but it was the "Persistent bitmap caching" that was causing my issue.ReplyDeleteAnonymousOctober 6, 2009 at 10:05 AMExcelente!! Después de probar y probar, realicé la conexión con la opción Themes deshabilitada y adios problema.Muchas gracias!!ReplyDeleteAnonymousOctober 8, 2009 at 2:51 PMThanks for the solution. Unchecking the "Themes" in the "Experience" tab worked for me.ReplyDeleteAnonymousNovember 19, 2009 at 2:16 PMFinally a solution that actually works without registry edits and file replacements! Thank you!ReplyDeleteAnonymousDecember 18, 2009 at 4:41 AMfyi: in my case (with the latest RDP), unchecking 'Visual Styles' (as themes are now dubbed) didn't do the trick -- But: unchecking 'Persistent bitmap caching' did!ReplyDeleteAnonymousJanuary 12, 2010 at 11:50 AMThanks you guys. My porblem is fixed. You are a hiro. Thanks thanks thanks...ReplyDeleteAnonymousJanuary 12, 2010 at 5:21 PMI'm trying to connect my Mandriva power pack 2010 with vista business it didn't work still the same problem with turning of my firewall (on Linux) and login as anyone still the same result.Do i have to open port 5900 on in my routerReplyDeleteAnonymousFebruary 22, 2010 at 6:49 PMI uncheck Both Theme and Persi
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 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 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. 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 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. The remote client may receive this error when the Remote host IP changes. Case 4: I had this p