Protocol Error Code 0x112b
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums because of a protocol error (code 0x112d) Answered by: Remoteapp - Because of a protocol error (code: 0x112b),
Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected
the remote session will be disconnected. Please try connecting to the remote computer again. Windows Server > because of a protocol error (code 0x112f) Remote Desktop Services (Terminal Services) Question 0 Sign in to vote Hi, I am hosting an application using Remoteapp (RDS farm) through RD gateway. Users from a
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
particular region are getting the below error. The reported user is using windows XP RDC 6.1. Please help. Remoteapp Disconnected Because of a protocol error (code: 0x112b), the remote session will be disconnected. Please try connecting to the remote computer again. Thanks in advance Vinu Tuesday, April 03, 2012 4:09 AM Reply | Quote Answers because of a protocol error this session will be disconnected windows 8 0 Sign in to vote Hi, Please install the Remote Desktop Connection 7.0 in your Windows XP. http://support.microsoft.com/kb/969084/en-us Make sure you have turned on CredSSP in your Windows XP. CredSSP is a new Security Support Provider (SSP) that is available in Windows XP SP3 by using the Security Support Provider Interface (SSPI). CredSSP enables a program to use client-side SSP to delegate user credentials from the client computer to the target server. (The target server is accessed by using server-side SSP). Windows XP SP3 involves only the client-side SSP implementation. The client-side SSP implementation is currently being used by Remote Desktop Protocol (RDP) 6.1 Terminal Services (TS). However, the client-side SSP implementation can be used by any third-party program that is willing to use the client-side SSP to interact with programs that are running server-side SSP implementations in Windows Vista or in Windows Server 2008. How to turn on CredSSP Fix it for me: Hotfix download link : http://go.microsoft.com/?linkid=9758284Let me fix it myself: Import
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
Because Of A Protocol Error Detected At The Client (code 0x2104)
company Business Learn more about hiring developers or posting ads with us Server Fault Questions
Because Of A Protocol Error This Session Will Be Disconnected Please Try Connecting Again
Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; protocol error detected at the client 0x1104 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 Remote desktop session ends abruptly with a https://social.technet.microsoft.com/Forums/windowsserver/en-US/c6ac861c-3200-4d76-923a-0c7db1630323/remoteapp-because-of-a-protocol-error-code-0x112b-the-remote-session-will-be-disconnected?forum=winserverTS “protocol error” up vote 4 down vote favorite Intermittently we get a problem where a remote desktop session will get disconnected with the error message “Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.” We are getting this with one server only which is running Windows Server 2008, connecting with Windows 7 clients. The session itself stays running, you just get disconnected, and you can http://serverfault.com/questions/200700/remote-desktop-session-ends-abruptly-with-a-protocol-error try and reconnect. Sometimes you get in for a while then it will kick you out. We are connecting from Windows 7 clients. We have tried connecting using Cord on a Mac and this works fine, so it's not like the session itself is corrupted. One problem is that there are some critical applications running under the session (I know, let's not discuss the idiocy of that), so we cannot reset the session in any way during the working day – so any diagnostics must have minimum impact. Thanks, Jon windows-server-2008 remote-desktop rdp share|improve this question asked Nov 11 '10 at 9:26 Jon 179236 Is this happening with all of your windows 7 client? –Not Kyle stop stalking me Nov 11 '10 at 17:18 Yes - once the session is in this 'state', I can't connect from any Windows 7 client (I don't have Vista/XP to try). I can connect using Cord from Mac or some other open source product on CentOS. –Jon Nov 15 '10 at 8:55 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote I had the same issue and luckily I found the solution on the social.technet.microsoft.com forum: ... Change the RDP Compression setting on the server to "Balances memory and network bandwidth" (recommended) or "Optimized to us
Problem: i had remote desktop up and running on a PC and then i got this: "because of http://computerboom.blogspot.com/2008/08/solution-because-of-protocol-error-this.html a protocol error detected at the client (code 0x1104), this session http://www.daishar.com/blog/archives/2005/10/because_of_a_pr.html will be disconnected. 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 protocol error or CLASSIC and see if the 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 because of a set the RDP client to NOT use the visual 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 replaceme
just fine, but then immediately (or very shortly) after logging in I'd be disconnected with the unhelpful error, "Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again." What does that mean, and what do I do if the error happens again when I try to reconnect as it says? off to search for an answer. Nothing useful there, and Microsoft's help for this message is complete useless. "Try connecting to the remote computer again. If you receive the same message, contact the server administrator." Reconnecting caused the same problem, and I'm the administrator. I tried contacting myself, but I couldn't get through. Now what? Today I finally found the solution. First let me say that this problem is not with a Windows CE machine, nor is it with the web interface to Remote Desktop. This is a Windows XP to Windows XP session. Anyway, on to the answer. I had already ruled out bad patches, bad software installations, and even went through a series of troubleshooting steps to "reset" terminal server. Out of the blue today, I got the idea that maybe the visual style I was using could cause this problem, as it might be a drawing issue that TS can't handle. I was using the "sgnome" style (don't remember where I got it but I think it was from deviantART originally), so I swapped back to the default Luna style and tried a TS connection. ... It worked! Okay, verify it. Previously, the act of opening an email in Outlook could cause the error, so I tried that. It still works. Tried replying to an email, still worked. Now my TS sessions are rock solid, I'm not getting kicked with a "protocol error", and all I did was change my style back to Luna. WTF? Well, I can't live with Luna as it's too boring, so I went searching for a different style. I settled on Reluna, after verifying that it didn't break anything else. Why did I think of visual styles? In the past I've had bad styles that broke other things