because of a protocol error, this session will be disconnected, Can not RDC to the server
When a user remote controls another user’s session using Remote Desktop Services Manager or Terminal Services Manager on a Windows Server 2008-based computer, and then stops remote controlling, one or both sessions are disconnected with the following error:
Remote Desktop Disconnected
Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.
CAUSE
This problem occurs if Remote Desktop Connection Client version 6.0.6001 or 6.0.6002 is used with the highest RDP Compression setting. Windows Server 2008 SP1/SP2 defaults to a lower RDP Compression setting, and thus will only exhibit the above symptoms if the setting has been changed to “Optimized to use less network bandwidth”, which is the maximum. Windows Server 2008 R2 defaults to the maximum RDP Compression setting.
WORKAROUND
Change the RDP Compression setting on the server to “Balances memory and network bandwidth” (recommended) or “Optimized to use less memory” using Group Policy. If using Windows Server 2008 R2 you may also choose “Do not use an RDP compression algorithm”. An alternative workaround is to use a different Remote Desktop Connection Client version than those mentioned above, however, this may not be practical. Below are instructions for making the change to the local group policy; if preferred you can use a domain group policy instead.
Windows Server 2008 R2
1. Logon to the Remote Desktop Services Session Host computer as an administrator
2. Start–Run gpedit.msc
3. In the left pane, under Computer Configuration, navigate to following:
Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
Windows Server 2008 (SP1 or SP2) or enterprices
1. Logon to the Terminal Services computer as an administrator
2. Start–Run gpedit.msc, click Continue if prompted by UAC
3. In the left pane, under Computer Configuration, navigate to following:
Administrative Templates\Windows Components\Terminal Services\Terminal Server\Remote Session Environment
4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change
STEPS TO REPRODUCE
Windows Server 2008 R2 x64
1. Install 2008 R2 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck “Require user’s permission”
5. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
7. In the administrator’s session, open up Remote Desktop Services Manager, right-click on the test user and choose Remote Control, click OK
8. After you are viewing the test user’s desktop, press Ctrl-Tab to end the Remote Control
Windows Server 2008 x64
1. Install 2008 Standard (Full Installation) x64 from DVD using defaults
2. Upon first logon, scroll down the initial configuration tasks window and click on Enable Remote Desktop
3. Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK
4. Open up Computer Management and create a test user, make them a member of the Remote Desktop Users group, on the Remote Control tab, uncheck “Require user’s permission”
5. Change RDP Compression algorithm to “Optimized to use less network bandwidth” using instructions above
6. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as administrator
7. Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user
8. In the administrator’s session, open up Terminal Services Manager, right-click on the test user and choose Remote Control, click OK
9. After you are viewing the test user’s desktop, press Ctrl-Tab to end the Remote Control
NOTE: This problem may occur when connecting to a Windows Vista or Windows 7 host under similar conditions. I have not tested this theory, however.
As always I welcome your comments/questions/corrections/suggestions/etc.
Thank you for reading.
References
http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/4523ce86-9a0b-4e6c-90d1-225ddda67ce5
April 30th, 2011 at 2:32 am
Nothing is as good as it seems beforehand.
March 25th, 2015 at 3:15 am
Nice post. I learn something totally new and challenging on sites I stumbleupon on a daily basis.
It’s always useful to read through articles from other authors and use
something from other sites.
March 28th, 2015 at 1:57 am
Woah! I’m really loving the template/theme of this site.
It’s simple, yet effective. A lot of times it’s very difficult
to get that “perfect balance” between usability and
visual appeal. I must say you have done a great job with this.
Also, the blog loads super fast for me on Chrome. Exceptional Blog!
July 8th, 2015 at 1:30 am
thanks
May 28th, 2016 at 5:27 pm
Have you ever thought about including a little bit more than just your articles?
I mean, what you say is valuable and everything.
But think of if you added some great photos or
video clips to give your posts more, “pop”! Your content is excellent but with
images and videos, this site could undeniably be one of the best in its field.
Terrific blog!
May 31st, 2016 at 2:55 pm
I’m not positive the place you are getting your information,
but good topic. I needs to spend a while finding out much more or figuring out more.
Thank you for fantastic info I was looking for this information for my
mission.
September 23rd, 2019 at 3:53 pm
donu0027t Stop thinking about Tomorrow
Ayad knowledge base » Blog Archive » because of a protocol error, this session will be disconnected, Can not RDC to the server