Protocol Error In Remote Desktop Connection
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums because of a protocol error this session will be disconnected windows 7 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 to because of a protocol error the client could not connect to the remote computer my windows server 2008 machine as the adminstrator, I often get the error message " because of a protocol error, the remote session
Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected
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 warning administrator rdp protocol error 0x1104 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 Sign in to vot
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
Because Of A Protocol Error This Session Will Be Disconnected Windows 10
about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask
Because Of A Protocol Error This Session Will Be Disconnected Server 2008 R2
Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign remote desktop protocol error windows 10 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 “protocol error” up vote 4 down vote favorite https://social.technet.microsoft.com/Forums/office/en-US/bcb264fa-9bd8-41dd-979b-51000e2b44ea/remote-desktop-protocol-error?forum=winserverTS 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 try and reconnect. Sometimes you get in for a while then it http://serverfault.com/questions/200700/remote-desktop-session-ends-abruptly-with-a-protocol-error 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 use less memory" using Group Policy. share|improve this answer answered Mar 4 '11 at 19:11 Regent 418179 Thank you! I will try th
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 https://forum.devolutions.net/topic2647-too-many-tabs--protocol-error.aspx disconnected. Please try connecting to the remote computer again." --Please see attached screenshot.I can't get any http://www.tripleginteractive.com/blog/productivity/remote-desktop-connection-protocol-error/ of the remote desktop 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 protocol error detail in case it is helpful: I'm not 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 because of a 2300x1400. Perhaps it can't handle many large remote desktop connections?Any help would 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: 13252 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: 13252 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: 13252 Hi, Thank you very
Spotlight Contact About Services Our Work Blog Contact Remote Desktop Connection protocol error We connect to remote computers via Remote Desktop Connection from time to time. Whether its to connect to a windows server or to connect to a desktop that is at a remote office. Some of our computers have a custom theme that will alter the look of the computer. These themes give the RDC problems. We get an error like Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again. We can connect to the remote computer just fine, but as soon as its done loading it throws the above error. Well, the error isn't exactly helpful. What has fixed the problem for us has been to go to the Advanced settings and then to Experience tab in the Remote Desktop Connection. Uncheck the Themes checkbox and this should solve your problem. If you continue to have problems from Windows 7 to another desktop/server, then you can try unchecking the Bitmap caching. + tripleGinteractive P 09/21/2009 t Productivity Crdc, remote desktop, windows 9 No Comments Share Twitter Facebook Google+ ← Splitting large files We like this: Autofill Forms → Leave a Reply Click here to cancel reply. XHTML: You can use these tags:
Current [emailprotected] * Leave this field empty ServicesResponsive Web Design Services Columbus Web Design Services Columbus, Ohio Web Development Services Search Engine Optimization Mobile Web Design WordPress Development Magento Ecommerce Development Web Hosting and Maintenance Recent Work Our Passion We’re driven by many passions: a passion for the Web, a passion for smart design, a passion for measured results, and a passion for creating and maintaining lasting relationships with our clients. Based in Columbus, Ohio, we utilize both best-in-class Web technologies and our own proprietary interactive practices to enhance our client’s business. Services Responsive Web Design Services Columbus Web Design Services Columbus, Ohio Web Development Services Search Engine Optimization Mobile Web Design WordPress Development Magento Ecommerce