Protocol Error Remote Desktop Connection
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My because of a protocol error this session will be disconnected windows 7 Forums Asked by: remote desktop protocol error Windows Server remote desktop protocol error 0x112f > Remote Desktop Services (Terminal Services) Question 0 Sign in to vote When connecting
Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected
to my windows server 2008 machine as the adminstrator, I often get the error message " because of a protocol error, the remote
Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
session will be disconnected ... "This always happens especially when I open a browser in the server machine, as the webpage is being loaded. After the the loading finish, connection will be safe.When I search for the event log in the server machine, I always finda because of a protocol error this session will be disconnected windows 10 warning administrator event:"Microsoft-Windows-TerminalServices-PnPDevices: Redirection of additional supported devices is disabled by policy."But following this event ID 36 and its solution http://technet.microsoft.com/en-us/library/cc775202%28WS.10%29.aspx, I cannot work around. I also change the remote desktop settings to cross out any PnP device (to exactly all devices will not be brought to the remote session) but problem still remains.For other possible solutions, I have update both client machine and server machine. I have tried different client machines, with OS being windows XP pro or windows server 2003. I have tried different versions of RD applications MSTSC.exe. I also patched a hotfix for windows 2008. In short, I have tried many official and non-official workarounds for this issue but no one works actually.I hope someone could give a real answer. Thanks! Saturday, February 20, 2010 1:41 AM Reply | Quote All replies 0
Protocol Error for RDP Sessions Brendan ThompsonPosts: 105 Hey
Because Of A Protocol Error This Session Will Be Disconnected Server 2008 R2
guys,After around 3 RDP sessions are opened in RDM remote desktop protocol error windows 10 i get hit with the follow: Because of a protocol error, this session will rdp protocol error 0x1104 be disconnected. Please try connecting to the remote computer again.Unfortunately once that happens the only way to fix it is by restarting https://social.technet.microsoft.com/Forums/office/en-US/bcb264fa-9bd8-41dd-979b-51000e2b44ea/remote-desktop-protocol-error?forum=winserverTS RDM. No matter how many times you try or even different RDP sessions it just won't get through.I am running the latest RDM on a 32-bit install of Windows 7. Are there currently any known errors?Thanks,Brendan -Brendan about 9 months ago Sjoerd van den https://forum.devolutions.net/topic24664-protocol-error-for-rdp-sessions.aspx BergPosts: 268 Yes, I have the same thing. Also colleagues of mine have this. It happens after more than x RDP tabs are opened. The number changes but mostly more than 8 sessions have to be opened.Could this be a memory issue?I know that in the past I could open 30 sessions easily. Cheers!Sjoerd (twitter.com/chanlerone) about 9 months ago David HervieuxPosts: 13254 Yes it's a memory issue. You could try RDM 64 bit. RDP 8 is really heavier on memory. This is other alternative:http://help.remotedesktopmanager.com/troubleshooting_largememoryawa.htm David Hervieux about 9 months ago Brendan ThompsonPosts: 105 Thanks Dave. Sadly the 32-bit OS is something that's enforced. -Brendan about 9 months ago David HervieuxPosts: 13254 The large memory aware setting could help you. David Hervieux about 9 months ago share a link to this post close
Too Many Tabs = Protocol Error? paulrogeroPosts: 6 Hi,I've noticed that if I open several tabs, around 5 or 6, I can no longer open any new tabs. When I try I receive the following error:"Because of a protocol error, this session will be disconnected. Please try connecting https://forum.devolutions.net/topic2647-too-many-tabs--protocol-error.aspx to the remote computer again." --Please see attached screenshot.I can't get any of the remote desktop http://stackoverflow.com/questions/31402343/remote-desktop-connection-protocol-error-0x112f connections to work. If I close some open tabs, then I can once again connect to another computer. However, even when Remote Desktop Manager can't open any more Remote Desktop connections, I can manually connect to more computers by using mstsc.exe outside of Remote Desktop Manager. So that makes me think the error lies with Remote Desktop Manager.Some more detail in case it is helpful: I'm not protocol error sure if the issue is memory related? By the time Remote Desktop Manager stops connecting to new computers it is using about 700-900 MB of RAM. That's not a problem for my computer as I still have many GB of RAM free, but may be the program doesn't like to use so much memory? Another factor might be my monitor size? I am connecting to Remote Desktops with a resolution of 2300x1400. Perhaps it can't handle many large remote desktop connections?Any help would because of a be appreciated.Thanks,Paulp.s. Love the program otherwise, its really good. SI 2013.02.18 - 04.40.51 PM.jpg Download about 4 years ago David HervieuxPosts: 13254 Hi, This is a know issue and we are still trying to find a solution. The problem is that Windows8 and Windows 2012 take about 150/200MB per connection. For now RDM is a 32 bit application and this is why we get the limitation. RDCMan has the same exact issue. This is very annoying and we are aware of that. David Hervieux about 4 years ago paulrogeroPosts: 6 Hi David,Thanks for the reply. I understand, hopefully a fix can be worked out! A x64 version would be great but I imagine that is a lot of work.Thanks,Paul about 4 years ago David HervieuxPosts: 13254 The problem with a x64 is that we have so many technology integrated, it's complex. However this is on the roadmap for sure. David Hervieux about 4 years ago grim334Posts: 2 for the time being you can try trick the application to use more memory, running this neat tool against the executable http://www.techpowerup.com/forums/showthread.php?t=112556. It worked for me on me on windows 8, right now I'm able to actually open more than 4 tabs at a time with RDM using around 1242MB of RAM with 11 tabs opened. about 4 years ago David HervieuxPosts: 13254 Hi, Thank you very much for the tip. We are currently working on a x64 version of RDM. We expect a beta in the middle of Ma
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 Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Remote desktop connection protocol error 0x112f up vote 3 down vote favorite When I try to connect to Windows 2012 Server using Remote Desktop Connection, I'm connected for about 1 sec. and then disconnected with following error: Because of a protocol error (code: 0x112f), the remote session will be disconnected. Until yesterday, connection was working fine with no error, no server changes. I never saw this error before. I tried to lower visual appearance settings in Experience panel (found as possible solution to similar error), but with no result. remote-desktop windows-server-2012 share|improve this question asked Jul 14 '15 at 9:07 Ondřej Šotek 634416 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted Server restart helped, I'm able to connect to server again. share|improve this answer answered Jul 14 '15 at 12:07 Ondřej Šotek 634416 this can also be done remotely if you have the appropriate rights via Sysinternals psshutdown –Peter Kirschner Jan 20 at 7:03 Or just shutdown /i, which also gives you a reboot option. –Josiah Jun 10 at 11:25 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged remote-desktop windows-server-2012 or ask your own question. asked 1 year ago viewed 5069 times active 1 year ago Blog Stack Overflow Podcast #92 - The Guerilla Guide to Interviewing Related 2Lync & Remote Desktop Connections1Can't get Remote Desktop Services installed on Windows 2012 server0Windows Server 2012 Remote Desktop Server slow GPO applied0Remote Desktop Service Deployment on Windows Server 20120Windows Server 2012 Change Password Without Remote Desktop1Timeout When Trying to Connect to AWS EC2 Windows 2012 Server with RDP/RDC with Windows 8