Protocol Error This Session Will Be Disconnected Windows 7
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: because of a protocol error this session will be disconnected. please try connecting to remote because of a protocol error this session will be disconnected please try connecting again computer again Windows 7 IT Pro > Windows 7 Miscellaneous Question 0 Sign in because of a protocol error detected at the client (code 0x1104) this session will be disconnected to vote Hi, When i remote desktop to a terminal server from windows 7 RC and run terminal services manager and
Because Of A Protocol Error Code 0x112f The Remote Session Will Be Disconnected
remote control a terminal server session (which i do quite a bit, as i am an IT Administrator) it connects to the session for a split second but then disconnects and displays the following
Because Of A Protocol Error This Session Will Be Disconnected Windows 10
error: because of a protocol error this session will be disconnected. please try connecting to remote computer again It does this every time i try and connect to a terminal server session.... annoying much! Anyone had a similar problem or is this alreadya known problem, i have search the forum but could not find anything related. Please could anyone help. Thanks. Thursday, May 07, 2009 8:06 AM Reply | Quote because of a protocol error the client could not connect to the remote computer Answers 0 Sign in to vote After three whole days of slamming my head in the car door, I have come to the conclusion that the problem is the mstscax.dll and mstsc.exe in the system 32 file and the other two files in the en-US or your language folder, that is the culprit, that is giving the unstable connection, reason being is that I switched that file with a known good working rdc in vista and it works flawlessly in windows 7, let me know if you need any help!! Marked as answer by Ronnie VernonModerator Sunday, May 10, 2009 2:49 PM Sunday, May 10, 2009 12:26 PM Reply | Quote All replies 0 Sign in to vote After three whole days of slamming my head in the car door, I have come to the conclusion that the problem is the mstscax.dll and mstsc.exe in the system 32 file and the other two files in the en-US or your language folder, that is the culprit, that is giving the unstable connection, reason being is that I switched that file with a known good working rdc in vista and it works flawlessly in windows 7, let me know if you need any help!! Marked as answer
Try to use Remote Desktop Manager 64bit. To because of a protocol error this session will be disconnected windows 8 do so, launch Remote Desktop Manager64.exe from the installation folder instead of Remote Desktop Manager.exe. https://social.technet.microsoft.com/Forums/windows/en-US/4523ce86-9a0b-4e6c-90d1-225ddda67ce5/because-of-a-protocol-error-this-session-will-be-disconnected-please-try-connecting-to-remote?forum=w7itprogeneral 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.
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 https://www.experts-exchange.com/questions/28288543/Remote-Desktop-Error-Because-of-a-protocol-error-this-session-will-be-disconnected.html Receive Real-Time Help Create a Freelance Project Hire for a Full http://serverfault.com/questions/200700/remote-desktop-session-ends-abruptly-with-a-protocol-error Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Experts Exchange > Questions > Remote Desktop Error - "Because of a protocol error, this session will be protocol error disconnected" Want to Advertise Here? Solved Remote Desktop Error - "Because of a protocol error, this session will be disconnected" Posted on 2013-11-07 VMware Windows Server 2008 Remote Access 5 Verified Solutions 52 Comments 10,313 Views Last Modified: 2013-12-01 I have a Terminal Server (W2008 32bit Std. / one of Virtual Machines in a VMWare box) session will be in one city running Industry specific application software and have a group of users in another city where they have been using Remote Desktop to connect to the Terminal Server to run that application software for more than a year w/o a problem. All of sudden starting a few weeks ago, ALL the users from another city (who uses remote desktop) is complaining that they are kicked off the session once or twice a day with the message "Because of a protocol error, this session will be disconnected". I googled this message and found numerous solutions to try, so I decided to post the question because I can't possibly try/apply all of those remedies. I am wondering if un-checking check boxes for "Visual styles" and "Persistent bipmap caching" will resolve the problem ... but then no user has changed the settings in remote desktop or know how to make these kind of changes. So that leaves one possibility - something happened to my terminal server settings.
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 Remote desktop session ends abruptly with a “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 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 use less memory" us