Error Code 0x1104
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 16:39:09 GMT by s_wx1094 (squid/3.5.20)
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 rdp because of a protocol error this session will be disconnected to fix the issue: 1. In your RDP client settings, remove all checkmarks from because of a protocol error the client could not connect to the remote computer Experience tab (see screenshot below). This seems to work for most people: 2. If you're running your RDP server on change security layer of the rdp-tcp session to "rdp security layer" 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 http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/remote-desktop-because-of-protocol-error-detected/bbe4276a-25ea-42a9-9c90-b41222cda1b0 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 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 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/ 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 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 f
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 https://www.experts-exchange.com/questions/26806932/Remote-Desktop-Protocol-error-code-0x1104.html Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > http://serverfault.com/questions/224950/windows-remote-desktop-protocol-error 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,838 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 protocol error 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 because of a 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 Active today 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 Active today 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 problem when i moved a server from a location to another. My 200
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