I am quite possibly wrong, but I think the ipfilter on netbsd is
set up so machines can get out, but not necessarily out get back
in...
I have had no success at getting to the machines behind my netbsd
box & ipfilter from out in the real world..

i think the easiest thing to do would be to make a SSH tunnel to
your netbsd box and have it try to connect to the windows box from
itself...

$ ssh -C -g -L5901:windows.box.behind.netbsd:5900 netbsd.box

and then VNC into the local work unix machine:1

if you have access to a unix machine somewhere at work...
if not, I know there exists a windows ssh that does the same thing,
but I don't know what it is...

this is how I do it, anyway...

hope this help?
jonathan

> Hi all,
> 
> I'm having some slightly unusual problems using VNC through a firewall, and
> I've searched around for the exact problem in the FAQ and mail archives but
> haven't come up with anything.  I'm attempting to use VNC in the following
> environment:
> 
>  vncviewer on
> NT Workstation          Home gateway/firewall        Home Windows box
>    at work             (NetBSD 1.4, ipfilter)         WinVNC server
>       |                      |        |                     |
>       +------ Internet ------+        +---------------------+
>                                               Home LAN
> 
> The NetBSD machine is using ipfilter to redirect incoming connections (i.e. on
> the interface connected to the Net) on port 5900 to port 5900 on the Windows
> machine on the LAN at home.
> 
> Now, I can run vncviewer fine on hosts on the home LAN, but I have problems
> when using vncviewer on my NT Workstation at work.  It connects OK and
> authenticates as usual, but doesn't seem to get any display data at all, and
> it simply disconnects after a few minutes.  Since VNC only uses one data port,
> I don't see why the connection would work fine to begin with and then suddenly
> stop allowing packets.  From the bit of experimenting I was able to do, it
> looks as though client data about mouse movement etc. is getting through to
> the server, but no display data is going back the other way.
> 
> I also tried using the Solaris VNC viewer on a Sun system at work, and had the
> same problem.  Here's its output (the "Connection reset" line appeared after a
> couple of minutes of apparent inactivity):
> <<
> VNC server supports protocol version 3.3 (viewer 3.3)
> Password:
> VNC authentication succeeded
> Desktop name "home"
> Connected to VNC server, using protocol version 3.3
> VNC server default format:
>   32 bits per pixel.
>   Least significant byte first in each pixel.
>   True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
> Warning: Cannot convert string "-*-helvetica-bold-r-*-*-16-*-*-*-*-*-*-*" to
> type FontStruct
> Using default colormap and translating from BGR233.  Pixel format:
>   8 bits per pixel.
>   True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
> Got 225 exact BGR233 colours out of 256
> Using 6 existing shared colours
> vncviewer: read: Connection reset by peer
> >>
> 
> BTW, running the VNC server on my work machine and the viewer at home works
> fine, in case that's relevant (which I kind of doubt).  Any ideas on what to
> do next in the way of troubleshooting?  I figure it's probably something to do
> with my firewall setup (which I can freely change).
> 
> Thanks in advance,
> Chris Edwards
> --
> "Nondeterminism means never having to say you are wrong."
> ---------------------------------------------------------------------
> 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