]
Subject: RE: Providing (Windows) VNC support to clients that have strict
corporate firewalls
Thanks. The "permitopen" option works really well on the sshd. The only
way I seem to be able to get around the loopback restriction is by running
the ssh client on an intermediate mac
al Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ossmann
Sent: Wednesday, January 16, 2002 3:26 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Wed, Jan 16, 2002 at 02:40:16PM -0500
OTECTED]]On Behalf Of Michael Ossmann
Sent: Tuesday, January 15, 2002 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Tue, Jan 15, 2002 at 10:10:18AM -0500, Chuck Renner wrote:
>
> WinVNC on ClientWS1 ---> SS
On Wed, Jan 16, 2002 at 02:40:16PM -0500, Chuck Renner wrote:
>
> Since VNCviewer states, "Internal loopback connections are not allowed", the
> implication is that there is a setting that WILL allow them, either in the
> source, or in the GUI settings. Is this the case?
I wasn't expecting this
ED]]On Behalf Of Michael Ossmann
Sent: Tuesday, January 15, 2002 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Tue, Jan 15, 2002 at 10:10:18AM -0500, Chuck Renner wrote:
>
> WinVNC on ClientWS1 ---> SSH o
On Tue, Jan 15, 2002 at 10:10:18AM -0500, Chuck Renner wrote:
>
> WinVNC on ClientWS1 ---> SSH on ClientWS1 port 5500 --> Internet --> sshd on
> MYFirewall port 443 --> VNCviewer on MyWS1 port 5500
>
> Have I got the idea right? If so, I should be able to do this without
> recompiling VNC at al
f Michael Ossmann
Sent: Monday, January 14, 2002 3:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Mon, Jan 14, 2002 at 02:34:16PM -0500, Chuck Renner wrote:
>
> There needs to be a way to change ALL Ports used by VNC, not
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ossmann
Sent: Monday, January 14, 2002 3:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Mon, Jan 14, 2002 at 02:34:16PM -0500, Chuck Renner wrote:
>
>
On Mon, Jan 14, 2002 at 02:34:16PM -0500, Chuck Renner wrote:
>
> There needs to be a way to change ALL Ports used by VNC, not just the ports
> it listens on. Ports used for outgoing connections should be able to be
> changed both on the command-line, and through the GUI interface. Since this
>
