> /sbin/service iptables status Firewall is not configured.
> problem is communication with that specific machine. Yes, I thought so. > a) create a tunnel on the gateway to SSH on the problem machine > b) create a tunnel (via the first tunnel) to VNC on the problem machine That might be what I did with the SSH command in my other posting ssh -f -N -C -T -l rvanovermeiren -L5902:localhost:5901 10.3.1.194 > Not "binded", tunneled. When I run the command again, it returns 'bind: Address already in use', so I thought I was binding ports to addresses. > Notice that this is using the SSH port for communication. That is why it works when connecting directly to the VNC server doesn't. Yes, so my box doesn't allow external connections for telnet or VNC. > You close the tunnel by closing the SSH connection. I can close my connection to the SSH gateway, but the tunneling connection stays there, and I can re-VNC. I guess I need to get the proc ID then kill it? _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
