Yes, Im running Windows ssh, and after all this frustration, I could write a
book on it.  At first I though ssh was the problem, but I am able to use it
on its own quite well. (and will never use Telnet again)
So I read that page about registry entries and made the entry and still no
dice.  Its interesting that the way it reads I expected the Reg. Keys to be
there and I would have to change the values.  Instead I have to create the
keys.  It does not tell me to create a dword, string or binary value and I
am assuming it is a decimal value rather than a Hex.
Either way I have both a VNC 3.3.3 entry and a Win VNC entry in the registry
so I created a key in each.  I have tried changing the type Dword to binary
etc. and still no go.  It keeps giving me the error local loopback
connections are not allowed.
I tried downloading a new version and re-installing and still nothing.
So now what do I try?

-----Original Message-----
From:   [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of David Brodbeck
Sent:   Wednesday, July 25, 2001 6:36 AM
To:     '[EMAIL PROTECTED]'
Subject:        RE: ssh, vnc and port monitor

You're right.  Good call -- I didn't spot it because I don't have a Windows
ssh server, so it's never come up.

-----Original Message-----
From: Miroslav Luptak [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 25, 2001 3:53 AM
To: [EMAIL PROTECTED]
Subject: Re: ssh, vnc and port monitor


David,

it seems than Neal is running VNC server on MS Windows machine!

Neal,

if the above is true, you have to create the following key
in the registry:
HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\AllowLoopback=1

The ssh command should look as follows:
ssh -L 5901:127.0.0.1:5900 remotehost

If you want to connect to the VNC Server ONLY through ssh, you can
consider setting the following key:
HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\LoopbackOnly=1

More info on keys at http://www.uk.research.att.com/vnc/winvnc.html

Regards,

Miroslav Luptak

>
> It sounds kind of like you already have a VNC server running on display 0
on
> your workstation.  If that's the case, use '5901:remotehost:5900' in your
> ssh command line, and try 'localhost:1' to connect to the tunnel.
Otherwise
> you'll have a conflict since ssh will be trying to use the same port
number
> the existing server is already using.
>
> Your ssh command line should look something like this:
>
> ssh -L 5901:remotehost:5900 remotehost
>
> Have a look at http://www.uk.research.att.com/vnc/sshvnc.html if you
haven't
> already.
>
> -----Original Message-----
> From: Neal Isaac [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 24, 2001 1:30 PM
> To: [EMAIL PROTECTED]
> Subject: RE: ssh, vnc and port monitor
>
>
> When I try localhost:0 VNC tells me loopback connections are not allowed.
> What am I doing wrong?
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of David Brodbeck
> Sent: Tuesday, July 24, 2001 9:51 AM
> To:   '[EMAIL PROTECTED]'
> Cc:   '[EMAIL PROTECTED]'
> Subject:      RE: ssh, vnc and port monitor
>
> You need to point VNC at the local end of the ssh tunnel, not at the
remote
> machine.  Make your VNC connection to 'localhost:0'.
>
> -----Original Message-----
> From: Neal Isaac [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 24, 2001 11:38 AM
> To: [EMAIL PROTECTED]
> Subject: RE: ssh, vnc and port monitor
>
>
> Can anyone help?
> This is the command I am entering on the client to redirect my VNC ports
to
> ssh.
> ssh -L 5900:remotehost:5900
> The server is running VNC and ssh and I can connect to the ssh terminal
and
> execute commands.  And I can connect to VNC.  My problem lies in getting
the
> VNC to use SSH.  I am trying on 2 machines on my network and using a
network
> monitor to monitor the communication.  When I issue the command, nothng is
> out of the ordinary to let me know that it is not accepted.  I open VNC
and
> connect.  However the port monitor tells me I am still using 5900 and 22
> (ssh) is not being utilized.  I can watch the data transfer occur and it
all
> happens on 5900.  I put a firewall in between and open up 22 but close
5900
> and I am unable to connect.
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to