0x1104 Remote Desktop Error
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 Experience tab (see screenshot below). remote desktop code 0x1104 This seems to work for most people: 2. If you're running your RDP server on a non-standard
Rdp Error 0x1104
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 rdp protocol error 0x1104 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 prompt window. From Start / Run enter: cmd - From the rdp because of a protocol error this session will be disconnected 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 this case would be to completely close out of Skype. Or simply Kill/Uninstall or temporarily disable
Because Of A Protocol Error Detected At The Client (code 0x2104)
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 (239) Slovak Blog (46) Links 1. FB Comments E-liquid Nicotine Calculator ETX.ca Jozef's Tools Mortgage Calculator Extra Payments Siri for Android SpeedX Fan Site August 2013 M T W T F S S « Mar Sep » 1234 567891011 12131415161718 19202122232425 262728293031 Archives October 2016 September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 Marc
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Cannot connect remote desktop because of a protocol error this session will be disconnected please try connecting again (code 0x1104) to Windows Server 2003 Windows Server > Windows Server because of a protocol error code 0x112f the remote session will be disconnected General Forum Question 0 Sign in to vote Hi, Have a Windows Server 2003 SP2 with
Change Security Layer Of The Rdp Tcp Session To Rdp Security Layer
latest patches and updates. The remote access to the server no longer works. I noticed that the PortNumber value of the HKLM\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp had been changed from 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/ 3389 to 3399. I changed it back to 3389 and rebooted the machine. It worked for a day os so then stopped working. I then noticed that the port number had been changed to 2288. I changed it back to 3389 and even though this value remains unchanged, a remote connection no longer https://social.technet.microsoft.com/Forums/office/en-US/9df2f4bd-0177-4cbb-ad02-96561d6b24e4/cannot-connect-remote-desktop-code-0x1104-to-windows-server-2003?forum=winservergen works and I get a messge (Beacuse od protocol error detected on the remote client (code 0x1104), this session was disconnected. (Roughly ttranslated from French). Have the same error from different PCs on the LAN or via a VPN connection. If I do a "telnet servername 3389" I get a message [hieroglyphics.. http://www.youngzsoft.com/cn/. A "netstat -no" indicates that the server is connected to 117.26.176.35, 117.26.180.162 and 120.40.251.213 via different ports. I suspect there is trojan installed but how do I go about detecting it and removing it. An antivirus scan did not detect anything. Moved by Roxana PANAITMicrosoft employee Tuesday, February 15, 2011 4:54 PM (From:Windows Server 2003 (et versions anterieures: Windows Server 2000, Windows NT Server)) Saturday, February 12, 2011 5:05 PM Reply | Quote Answers 0 Sign in to vote Hi, 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.
SonicWALL User Sorry, we are having issues processing your request. If you own the SonicWALL https://support.software.dell.com/kb/sw12397 product requested please confirm that you have registered your product https://www.experts-exchange.com/questions/26806932/Remote-Desktop-Protocol-error-code-0x1104.html at My SonicWALL . If you have already registered your product then please contact Customer Service directly for further assistance at customerservice@software.dell.com. Continue Search Sign In Sign In Create Support Account Products ActiveRoles Boomi Change Auditor Foglight Identity Manager KACE Migration protocol error 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 & Management Database Replication & Backup Endpoint Management Mobile Workforce Management Overview Desktop Virtualization Enterprise Mobility because of a 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 info
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 Careers Vendor Services Groups Website Testing Store Headlines 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,797 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 Active 1 day ago 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 1 day