#97 Can not connect via SSH and port forwarding

[Anonymous]

I just upgraded to version 2.0b4, and I can no longer
connect to work via SSH port forwarding. When I try to
connect I get the following error.

"Could not connect to server localhost: 11800"

I verified SSH port forwarding is working correctly by
downloading "VNCViewer" and connecting to work
successfully. I don't like VNCViewer and think your
application is far better.

One other thing to note: I ran Ethereal to see what is
happening on my connection, and found out that no
packets are sent on my Ethernet connection when I try
to connect to work. So it seems to be related SSH port
forwarding.

I hope you can take a look at this problem.

Thanks,

David Whalen

[Bill McGonigle]

Logged In: YES
user_id=167489

I see this also. 2.0b2 works fine. David can you confirm?
I'm running Mac OS X 10.3.9. 2.0b4 works fine on the local
net, sans SSH.

Darn, I really liked the sorted machine list! :)

[Bill McGonigle]

Logged In: YES
user_id=167489

OK, I figured out what's going on here - it's a notation
change.

With b2 and lower your could put a port number in the
display field and it was smart about figuring out if it was
a port number or a display number.

Now you have to specify localhost:12345 instead of a display
number. I guess somebody could have 12345 VNC sessions
running and not be able to address it that way.

So, WFM.

[Nobody/Anonymous]

Logged In: NO

I've noticed this behavior using build 2.0b4 in a MacBook. Connections work
perfectly across a local network, but when connecting to an ssh tunnel one of
three things happen:
1) unable to connect error,
2) about 20 pixels deep of a garbled screen is displayed before the
connection drops, or
3) completely bank (all black) window displayed with no change.

When I switch the 2.0b4 build to open "using Rosetta" in the application file
info window then these problems go away and I am able to successfully
connect over an ssh tunnel.

During my testing of this problem I set up a single ssh tunnel to a vnc server.
I first set the 2.0b4 build to run natively on my MacBook and CofVNC
demonstrated the problems listed above. Then using the same ssh tunnel, I
set the 2.0b4 build to run using Rosetta and am able to successfully connect
over the same ssh tunnel that was previously failing.

My guess is that there are some byte order problems in the Intel codebase.

-- Michael Richmond