Dale:
        Heya. I've some quick questions and suggestions about
your setup:

> I have: A win2000 box, diamond 192.168.0.1, running openssh 3.4p1 under
> cygwin, and winVNC 3.3.3 R9, both running as a service.
>
> I can ssh OR VNC from another win200 box, amethyst 192.168.0.14; or a mac
> OSX (10.0.3) 192.168.0.3 named OSX to diamond.
>
> From amethyst (I know it much better than the mac) I connect using either
>
> SSH.com's client
>
> Tunneling:
> Name                            VNC
> Listening Port                  5911
> Dest Host                       192.168.0.1
> Dest Port                       5910
> Allow Local Connection  Either Yes or No

        This looks to me like it's going to open port 5911 on your
client machine (amethyst), tunneling all the data there to port
5910 on 192.168.0.1 (diamond).

> cygwin/openssh using
>
> ssh -C -L 5910:192.168.0.1:5911 [EMAIL PROTECTED]

        This, on the other hand, is going to open port 5910 on
your client machine, and tunnel data to port 5911 on 192.168.0.1
after it connects to "[EMAIL PROTECTED]".

        So...is WinVNC on diamond listening to display 10 (5910)
or display 11 (5911)?

> and it connects fine.  However with the vncclient 'localhost:11' I just
> hang doing nothing.

        After you start the SSH tunnel on amethyst, what do you
see when you "telnet 192.168.0.14 5910"? Do you see the RFB response
from the VNC service on diamond? How about if you "telnet 127.0.0.1
5910"? Whichever works, try pointing your VNC viewer on amethyst
to the same IP address.

        Lastly, try giving this a whirl. Presuming that WinVNC is
running on diamond listening to port 5910, start SSH on amethyst:

        ssh -C -L 5910:127.0.0.1:5910 [EMAIL PROTECTED]

        Since your WinVNC server is setup to AllowLoopback, this
should work for you. Good luck!

-Scott
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to