ok, I realized that vnc networking is not as simple as I made it at
first, and it is not as simple as running a ssh daemon on your server,
my apologies for the previous question.
So now my fedora fc13 is running TigerVNC, /etc/sysconfig/vncservers
has been edited, vncserver is running, and iptables is accepting
connections at the 5902 port.

I  also checked that the apps "VNC viewer" and "MochaVNC" work
perfectly - but I want to use iSSH since I prefer your app...

The configuration I created for a SSH/VNC shows at last green light,
but when I run it I see the message "Opening SSH tunnel" and nothing
else.

can you help me debug what the problem is?

thanks

alessandro

Usually I get that situation when either I am using the wrong port or VNC server is not running on the host. I occasionally get it on a busy/slow connection too.

Recommend you use iSSH to login with the shell console to check if VNC Server is running. If so, next check the port settings for VNC in your iSSH configuration for that host.
If that still doesn't work, try using a PC to do the same job as a test.
Linux and Mac would be something like
ssh user@machineIP -L 590X:localhost:5902
Where you substitute the user and the machineIP for the ones on your VNC server host and X would be whichever port you want to listen with on your local machine.
You would then open localhost:X with VNC Viewer on Linux or Chicken of the VNC on Mac. (you may prefer other viewers)
For Windows, open Putty, go in to the options and look for SSH tunnels. Set it up in the same format as earlier (590X:localhost:5902) then launch the Putty session.
Finally launch your VNC viewer software and point it at localhost:X or port 590X depending on its settings.
If it works with PC but not with iSSH then there is something not quite right with your iSSH settings. I can vouch that iSSH works well with TigerVNC and also VNC Server as I use both regularly.

Best regards,

Nick

On 27 Apr 2012, at 18:14, alexxx <alexxx.ma...@gmail.com>wrote: