[cotvnc-devel] [ cotvnc-Bugs-1017710 ] Connecting to PC running TightVNC server - Inflate error
Project superseded by http://chicken.sourceforge.net/
Brought to you by:
smeger
From: SourceForge.net <no...@so...> - 2005-08-23 08:23:16
|
Bugs item #1017710, was opened at 2004-08-27 09:25 Message generated for change (Comment added) made by smeger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507159&aid=1017710&group_id=64347 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Networking Group: v2.0 >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jason Harris (smeger) Summary: Connecting to PC running TightVNC server - Inflate error Initial Comment: I am connecting to a Windows XP machine which is running TightVNC server 1.2.9. When I launch CotVNC 2.0b2 and enter in the IP and password of the Windows machine, I get the error "Connection Terminated. Inflate error: unknown compressions method." On the Windows machine, the VNC server indicates that a connection was made, but on the Mac, nothing shows up. This error did not occur in 2.0b1. My e-mail address is mic...@pu... ---------------------------------------------------------------------- >Comment By: Jason Harris (smeger) Date: 2005-08-23 01:23 Message: Logged In: YES user_id=351330 Resolved for Chicken 2.0b3. ---------------------------------------------------------------------- Comment By: Robert Engström (robo-x) Date: 2005-06-27 03:59 Message: Logged In: YES user_id=836162 I tried the latest version of COTVNC 2.0b2 and I can't connect to the Mac using Apple Remote Desktop in Tiger. It can connect but I get this error: Zlib inflate error: invalid literal/length code After some tests I figured out what was causing the problem. I used 256 colors on the client because using VNC over a modem is slow. Having less colors makes it a little faster. Anyway when I changed the connnection profiles to let server decide it works but with million of colors. Possible to fix this in a future version of COTVNC? //Rob ---------------------------------------------------------------------- Comment By: Jason Harris (smeger) Date: 2004-12-07 18:30 Message: Logged In: YES user_id=351330 Fixed in CVS for 2.0b3. ---------------------------------------------------------------------- Comment By: Jake Robb (jakerobb) Date: 2004-12-03 10:13 Message: Logged In: YES user_id=849257 Confirm this problem here. I can only connect to a TightVNC server 1.2.9 with Tight encoding disabled. Tight being the most efficient encoding, I'd like to see this fixed! -Jake ---------------------------------------------------------------------- Comment By: Gray Watson (graywatson) Date: 2004-11-19 16:01 Message: Logged In: YES user_id=24124 Removing "tight" encoding seems to resolve this problem: Select 'Connection Profiles' from the Connection menu and desellecting Tight on the Encodings tab. The changes do not seem to take effect until to restart the program. ---------------------------------------------------------------------- Comment By: Jeff (dane98961) Date: 2004-11-04 10:09 Message: Logged In: YES user_id=1152609 For what it's worth, My workaround is simpler: I only disable "TIGHT." "ZRLE" appears to work fine. When I enable TIGHT, I get the same inflate error. The configuration of my Windows machine is 2000 with service pack 3. I am connected to it over a Cisco VPN tunnel. ---------------------------------------------------------------------- Comment By: Jeff (dane98961) Date: 2004-11-04 10:08 Message: Logged In: YES user_id=1152609 For what it's worth, My workaround is simpler: I only disable "TIGHT." "ZRLE" appears to work fine. When I enable TIGHT, I get the same inflate error. The configuration of my Windows machine is 2000 with service pack 3. I am connected to it over a Cisco VPN tunnel. ---------------------------------------------------------------------- Comment By: Jeff (dane98961) Date: 2004-11-04 10:06 Message: Logged In: YES user_id=1152609 For what it's worth, My workaround is simpler: I only disable "TIGHT." "ZRLE" appears to work fine. When I enable TIGHT, I get the same inflate error. The configuration of my Windows machine is 2000 with service pack 3. I am connected to it over a Cisco VPN tunnel. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-09-20 12:42 Message: Logged In: NO I can duplicate this error as well on my system. XP running TightVNC 1.2.9, inflate error. er...@sf... ---------------------------------------------------------------------- Comment By: moon caine (mooncaine) Date: 2004-08-31 11:26 Message: Logged In: YES user_id=755294 I can confirm this on my setup: connecting to TightVNC 1.2.8 on Windows 2000 PCs from Panther OSX with CotVNC 2.0b2 ... I see the same error dialog. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-08-30 08:39 Message: Logged In: NO Disabling both ZRLE and Tight encodings in the profile allow for connections to be made to a Windows XP machine running TightVNC server over a LAN. However, enabling both settings results in the same "inflate" error with 2.0b2. mic...@pu... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-08-27 19:32 Message: Logged In: NO My situation was over our office LAN, *not* a VPN. On Monday morning, I will try it again with both those options unchecked in CotVNC. mic...@pu... ---------------------------------------------------------------------- Comment By: Jason Harris (smeger) Date: 2004-08-27 10:56 Message: Logged In: YES user_id=351330 Clay, you say this works if you don't use the VPN tunnel. Does it work with ZRLE and Tight enabled? In other words, is it the tunnel causing the problem or the encodings? I'll test against TightVNC and see if I can duplicate - we've done all of our testing against the current RealVNC. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-08-27 09:47 Message: Logged In: NO Sorry if this winds up being a double-post - I can't see my post show up. I have figured out a work around for this bug. I was having the same problem as you. Disable the ZRLE and Tight encodings in your profile, and try again. Then you can connect. Clay cl...@ty... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-08-27 09:45 Message: Logged In: NO I HAVE FIGURE OUT A WAY AROUND THIS ERROR - I had the exact same problem and scenario. When I edited my profile to disable the ZRLE and the Tight encodings, and used that profile to connect to the Win XP client, I successfully connected. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-08-27 09:37 Message: Logged In: NO I just got this same error, same situation, connecting to Win XP client running TightVNC 1.2.9, from my Mac over a VPN and I'm using CotVNC 2.0b2 See my thread after yours. Cl...@ty... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507159&aid=1017710&group_id=64347 |