Protocol Error Remote Desktop 0x1104
Contents |
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 fix the issue: 1. In your RDP client settings, remove all checkmarks from because of a protocol error detected at the client (code 0x2104) Experience tab (see screenshot below). This seems to work for most people: 2. If you're running change security layer of the rdp-tcp session to "rdp security layer" your RDP 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. because of a protocol error this session will be disconnected windows 7 In that case, you'll need to find out what else may 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 because of a protocol error the client could not connect to the remote computer 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 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
Because Of A Protocol Error (code 0x112f)
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 win7 client. Reply↓ inexpensive on June 2, 2016 at 3:16 pm said: ZW Reply↓ Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Post Navigation ← Previous Post Next Post → Search for: About Me Profile: Categories English Blog (248) Slovak Blog (46) Links 1. FB Comments Code Learning Videos ETX.ca Jozef's Tools Mortgage Calculator Extra Payments Online Documentaries Recipes of your dreams Siri for Android
SonicWALL User Sorry, we are having issues processing your request. If you own
Because Of A Protocol Error (code 0x112d)
the SonicWALL product requested please confirm that you have registered because of a protocol error this session will be disconnected please try connecting again your product at My SonicWALL . If you have already registered your product then please because of a protocol error detected at the client 1204 contact Customer Service directly for further assistance at customerservice@software.dell.com. Continue × Support Forms Under Maintenance Submitting forms on the support site are temporary unavailable 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/ 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 all Products Solutions Application https://support.software.dell.com/vworkspace/kb/85618 & 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 Groups My Profile Policies & Procedures Professional Services Technical
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 http://serverfault.com/questions/224950/windows-remote-desktop-protocol-error 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; http://www.chicagotech.net/remoteissues/code0x1104.htm 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 protocol error 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 because of a 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
When attempting to access a remote computer using RDC, you may receive this 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" 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 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: Can’t 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.