OK, the behaviour was just the same even when doing a reverse connection from
the server behind the firewall. Also strange is that I have an X server on
the same machine that was running WinVNC, with the NAT set up in exactly the
same way for port 6000 as for 5900, and that's always worked fine.
Anyway, here's the good news: I've just upgraded to NetBSD 1.5 on my home
gateway, which includes ipfilter v3.4.9, and VNC now seems to be working fine
through the firewall. Thanks Jonathan and Carlyle for your help and
suggestions - I expect I'll want to have a look at ssh anyway.
--
Chris Edwards
--
"Every program has at least one bug and can be shortened by at least one
instruction -- from which, by induction, one can deduce that every program can
be reduced to one instruction which doesn't work."
---------------------------------------------------------------------
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
---------------------------------------------------------------------
