Hello,
I've been using tightvnc over SSH for a while now and lately I wanted to
add more security by using the -localhost switch on the vncserver
command. Since that change my clients can't connect anymore.
One thing I noticed in the vnc log files (before I added the -localhost
switch) is that for the line that says:
Got connection from client aaa.bbb.ccc.ddd
I get the full IP address of the system running the tightvnc server, as
opposed to 127.0.0.1, which makes me think that maybe this is why it
does not work when I enable the -localhost switch. The IP address is
the right one, since tunneling is used, but I don't understand why it is
the system's IP address instead of '127.0.0.1'. Is this something
related to the way I do the SSH tunneling?
With the -localhost switch, in the vnc logfile I simply get:
X connection to :2.0 broken (explicit kill or server shutdown).
The SSH tunnel is created using the Jsch SSH libraries (local port
forwarding), and the VNC viewer on the client's system is the tightvnc
Java viewer.
Any information about this would be much appreciated.
Regards,
Andre
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
