Nick:
Heya. Sorry for the late reply. Most firewalls that a
company would use come "out of box" with only a handful of
external services reachable. That is, the firewalls will allow
anyone to connect to FTP, Telnet, HTTP, HTTPS and SMTP. That's
about it. For example, an "ICSA approved" firewall:
http://www.icsalabs.com/html/communities/firewalls/certification/criteria/criteria_3.0a.shtml
Anyhow. As you'll noticed in the above, the actual
*content* of the data connection is not a requirement for most
firewall ceritifications, nor is content-based filtering a
capability of most firewalls, either. So, I'm betting that
the firewall at your work allows anyone to connect to any
server that's listening on the default ports of FTP, Telnet,
etc, etc.
My suggestion, then, is to trick your workplace firewall
by changing the mapping of your LinkSys box. So, have port-80
(which is the default for HTTP servers) on the outside of your
LinkSys box go to port 5900 of your home-LAN VNC machine. Then,
from work, "telnet a.b.c.d 80" and see if it connects. If it
does, then you can get the VNC viewer to connect as well. I'm
pretty sure your LinkSys box lets you map port-A to port-B
(some lower-end boxes won't).
Good luck!
-Scott
> Thanks for everyone's help. I had someone else try at a different company
> to get to the home PC and they were able to get connected via the Java
> viewer. The ports must be blocked at my company...
>
> Thanks again,
> Nick
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
