how to solve the "zlibinstream:exceeded bytesIn" error in vnc
Asked Answered
H

8

13

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 ?

Homonym answered 2/11, 2014 at 7:43 Comment(0)
V
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.

Vichyssoise answered 31/12, 2014 at 10:28 Comment(4)
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.Reeding
Ack, maybe not. The problem just came back (22 days later) and FullColour is still true.Reeding
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. thanksTheorist
funnily changing FullColour to "False" did it for me. So I'm not really sure, if this has anything to do with it.Becca
R
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.

Robichaud answered 17/3, 2017 at 18:31 Comment(2)
saved my day! Not sure, why there is no real fix for this issue yet!Parisian
I made this fix on the fly and viewer is back. Let see if works permanently!Savour
C
4

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

Callum answered 5/4, 2017 at 15:37 Comment(1)
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.Logistics
R
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.

Reeding answered 31/7, 2015 at 8:59 Comment(1)
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.Reeding
D
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.

Dinin answered 10/12, 2014 at 2:15 Comment(0)
D
2

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

Dispensable answered 18/4, 2018 at 6:27 Comment(0)
G
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.

Georg answered 14/5, 2015 at 16:4 Comment(0)
T
0

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

Titration answered 1/5, 2015 at 4:51 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.