On Sun, 3 Dec 2000, Jim Brown wrote:
> With Multi NIC, W/O 'Allow Loopback';
>
> VNC Listens on IPANY 0.0.0.0 (NIC # N,...) Ports 580x/590x
>
> SSHD listens on LOOPBACK 127.0.0.1 Ports 580x/590x,
> Forwards via NIC # N Ports 580x/590x Direct (590x <> 590x)
>
> All is well.
>
>
> With 'Allow Loopback';
>
> VNC Listens on IPANY 0.0.0.0 (NIC # N,...) + LOOPBACK 127.0.0.1 Ports
>580x/590x
>
> SSHD listens on LOOPBACK 127.0.0.1 Ports 580x/590x,
> Forwards via NIC # N Ports 580x/590x Direct (590x <> 590x)
>
> Thus both Service/Appl. is trying to OWN 127.0.0.1/590x !
No. This is not what is happening. If AllowLoopback is not set then
WinVNC still listens for connections on any interface but closes those
incoming from the local loopback interface.
> If I set the value of the LoopbackOnly registry key to 1 on my SSH2
> server, then try to run the vncViewer utility from my client machine, I
> cannot connect. No error message, nothing.
There is now LoopbackOnly registry key. What do you mean when you say "I
cannot connect. No error message, nothing." If there is no error
message, what is indicating the failure to connect? You will get a
completely silent disconnect by the viewer if you have accidentally
forwarded the SSH tunnel to the wrong port at the VNC server end. The
viewer will happily connect to the local SSH client, which will connect to
the server, which can't then connect to the VNC server and so the whole
connection will be closed again, silently.
Cheers,
Wez
---------------------------------------------------------------------
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
---------------------------------------------------------------------
