Because Of Protocol Error Remote Desktop
Contents |
One games Xbox 360 games PC remote desktop because of a protocol error windows 7 games Windows games Windows phone games Entertainment All
Remote Desktop Because Of A Protocol Error This Session Will Be Disconnected
Entertainment Movies & TV Music Business & Education Business Students &
Rdp Protocol Error
educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Remote Desktop Connection Because Of A Protocol Error This Session Will Be Disconnected
Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft remote desktop connection because of a protocol error detected at the client Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Try to use Remote Desktop Manager 64bit. To remote desktop protocol error code 0x1104 do so, launch Remote Desktop Manager64.exe from the installation folder instead of Remote Desktop Manager.exe. https://support.microsoft.com/en-us/kb/2273487 Solution 2 Uncheck Bitmap Caching and Themes under the Experience tab in the properties of the RDP session. Uncheck Themes And Bitmap Caching Solution 3 http://help.remotedesktopmanager.com/troubleshooting_protocolerror.htm Close Remote Desktop Manager,rename default.rdp file in My Documents to default.old, restart Remote Desktop Manager and try to connect with RDP. Solutions 4 Login in to the target machine,by directly going to the console of that server or by any tool like VNC so that we can get access to that machine. After connecting: 1.Right Click on the Desktop2.Select the Properties3.There DropDown the Themes and select the theme other than the current one.4.Click on Apply, OK Now try to connect that machine remotely.
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 http://serverfault.com/questions/200700/remote-desktop-session-ends-abruptly-with-a-protocol-error hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question https://forum.devolutions.net/topic2647-too-many-tabs--protocol-error.aspx _ 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 Remote desktop session ends abruptly with a “protocol error” up vote 4 down vote favorite Intermittently we protocol error 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 will kick you out. because of a 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 this the next time it occurs. I've h
Backup and much more. You are one click away from getting the most out of your Remote Desktop Manager experience. Create your account and have access to awesome new features! Log in Create free account Forgot password Forum / Remote Desktop Manager - Bug Report 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 to the remote computer again." --Please see attached screenshot.I can't get any 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 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 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: 13176 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,Th