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:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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

share|improve this question
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

I had the same issue and luckily I found the solution on the 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
Thank you! I will try this the next time it occurs. I've had a paid support case open with Microsoft for months now...jumped through 100 hoops with no resolution. I'll report back the result the next time the error pops up. – Jon Mar 15 '11 at 14:08

A possible test is to see if this occurs with Windows 7 clients connecting through a different IP network/subnet (if the current situation occurs with local network clients).

share|improve this answer

Your Answer


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 or ask your own question.