Protocol Error Detected Client Code 0x1104
Contents |
SonicWALL User Sorry, we are having issues processing your request. If you because of a protocol error detected at the client (code 0x2104) own the SonicWALL product requested please confirm that you
Change Security Layer Of The Rdp-tcp Session To "rdp Security Layer"
have registered your product at My SonicWALL . If you have already registered your product because of a protocol error the client could not connect to the remote computer then please contact Customer Service directly for further assistance at customerservice@software.dell.com. Continue × Support Forms Under Maintenance Submitting forms on the support site are
Because Of A Protocol Error Detected At The Client 1204
temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for 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 rdp because of a protocol error this session will be disconnected all Products Solutions Application & Data Integration Big Data Analytics Business Intelligence Cloud Management Data Protection Overview Backup and Recovery Deduplication and Compression Database Development 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
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 20:13:51 GMT by s_wx1087 (squid/3.5.20)
Problem: i had remote desktop up and running on a PC and then i got this: "because of a protocol error http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html detected at the client (code 0x1104), this session will be disconnected. http://serverfault.com/questions/224950/windows-remote-desktop-protocol-error please try connecting to 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 or CLASSIC and see if the protocol error 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 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 because of a 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 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'
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 other application / program is using port 3389 ... Can you try to rdp from the same LAN? I had a similar issue and the rdp port was assigned / occupied by another app. Check for and uninstall the conflicting app or change the RDP port on your server. http://support.microsoft.com/kb/306759 share|improve this answer answered Jan 21 '11 at 0:12 rihatum 1,9002139 add a comment| Your Answer draft saved draft discarded Sign up