John:
Hello! Quick thought for you:
> 4. Both will connect through the router to my VNC server at work
> (Linux) w/o zebedee just fine.
I suspect that the firewall at your workplace is specifically
configured to allow you to connect to some specific port range on that
Linux box (maybe just the standard 590x ones). If you telnet'ed to,
say, that machines port 25 (SMTP) it's *probably* blocked. Well, hee,
it should be. :)
> That connection allows me to make zebedee port conf
> changes from home. After each change, I kill and restart
> zebedee on the linux box and check the log file to make certain that
> Zebedee is listening on the new port
Yes, but does your workplace firewall allow you to connect to
the port you chose?
Try this...since connecting to the VNC server appears to work,
stop and restart the VNC server and have it listen to port 45678,
rather than it's default at 5900. *Then* startup ZeBeDee on the server
and have *it* listen to 5900. You should now be able to start ZebeDee
on one of your home Windows systems and connect to ZebeDee at the server.
In other words, it sounds as if your workplace firewall is
allowing an incoming connection from your home-LAN to a specific
port (probably 5900) on the Linux box. What you *do* with that
'firewall hole' is up to you: I strongly doubt that your workplace
firewall (or your IPS's firewall) is smart enough to distinguish TCP
packets sent by VNC and the TCP packets sent by ZeBeDee.
Good luck!
-Scott
---------------------------------------------------------------------
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
---------------------------------------------------------------------
