Protocol Error 0x1104 Code
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From
Because Of A Protocol Error Detected At The Client (code 0x2104)
My Forums Answered by: Remote Desktop Encryption error at the because of a protocol error (code 0x112f) client Windows 7 IT Pro > Windows 7 Networking Question 0 Sign in to vote change security layer of the rdp-tcp session to "rdp security layer" I'm suddenly receiving a critical remote desktop error at the client stating the following (it differs from time to time) "Because of an error in
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
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. Please try connecting to the remote computer again." I've been running on the same windows 7 64 bit build on
Rdp Because Of A Protocol Error This Session Will Be Disconnected
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 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,
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 https://www.experts-exchange.com/questions/26806932/Remote-Desktop-Protocol-error-code-0x1104.html Hire for a Full Time Job Ways to Get Help Expand Search http://serverfault.com/questions/224950/windows-remote-desktop-protocol-error 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 protocol error 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 because of 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:divers
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