12

Every now and then I get the "zlibinstream:exceeded bytesIn" error when trying to connect to my server through my vnc. Why do I get this error and how can I solve it when I get it - without restarting my server ?

yehudahs
  • 2,488
  • 8
  • 34
  • 54

8 Answers8

18

Came across the same issue a couple of times. I am not aware of permanent fix, but for a quick one just change colour to Fullcolour.

For me in VNC Viewer it was in options/Expert/FullColour to true.

Burpy Burp
  • 459
  • 3
  • 12
  • Turning FullColour to true fixed it for me too. As a test, I tried turning FullColour back to false and the problem came back. Strange that this problem just started today after 1.5 years of exactly the same usage. – jfritz42 Jul 09 '15 at 20:33
  • Ack, maybe not. The problem just came back (22 days later) and FullColour is still true. – jfritz42 Jul 31 '15 at 08:48
  • While I can't definitively say this is the cause, we have just upgraded Cisco AnyConnect VPN client from 3.x to 4.1.08005 and I am noticing this error for the first time. As you say, changing the colour settings seems to have made it go away for now. thanks – Pancho Dec 02 '15 at 07:33
  • funnily changing FullColour to "False" did it for me. So I'm not really sure, if this has anything to do with it. – blaucuk Jul 17 '23 at 11:49
5

Another quick fix (for Mac):

Reading the other responses and trying out a few, I feel toggling random Properties/Options will "solve" this problem. Do the following for Real VNC on Mac:

Options -> Picture Quality -> High. Then Set it back to Automatic.

K.K
  • 2,647
  • 1
  • 26
  • 32
4

In my case the solutions is just to change quality to Low. Seems to work fine.

CROSP
  • 4,499
  • 4
  • 38
  • 89
  • This worked for me, did you ever find a more permanent fix? I'd rather the picture quality not stay low...Edit: Actually, I changed it back to high or automatic or anything, it seems to still work. How strange. – Brandon Nov 06 '17 at 21:31
3

What worked for me was to turn off "Adapt to network speed (recommended)" (under Options->Display) and then move the compression slider to the left from "All available colors, medium compression" to "Hundreds of colors".

Prior to this, Burpy Burp's answer of changing options/Expert/FullColour to true temporarily fixed the problem but it came back 22 days later.

jfritz42
  • 5,913
  • 5
  • 50
  • 66
  • Even this failed eventually. I had to change it back from "Hundreds of colors" to "All available colors, max compression". It seems like every once in a while it's necessary to force a mode change in order to work around this issue. The start/end mode is unimportant. – jfritz42 Sep 12 '16 at 17:17
2

This seems to be related with timing. On my mac, I'm having the same issue and usually waiting for a while and retrying is the only thing that works for me. It always comes back but not an immediate solution.

shadowyman
  • 215
  • 3
  • 11
2

Color level Full didnt resolve the issue but when set Options-Picture Quality High instead of Automatic resolved.

Sham Naragund
  • 21
  • 1
1

Just for the googlers out there that find this question: Changing the "prefered encoding" to something other than "ZRLE" (I used "hextile")is what solved the issue for me.

Rob
  • 11
  • 2
0

Opening the options dialog without changing anything did it for me. Baffled.

dmvianna
  • 15,088
  • 18
  • 77
  • 106