I'm pretty sure it's a problem with Roadrunner. I have one user connecting
using zebedee from his home using the Roadrunner "1-way" product. I can see
that his Windows 95 generated zebedee connection (from his home) to my linux
"VNC server" at work is working by reading the log file created by the zebedee
server. I can also see that he disconnects normally. I'm using linux and generating
multiple private VNC desktops on one box.
So:
1. I ask him to connect, he does.
2. I ask him to disconnect, he does.
3. He and I use identical vncviewer.zbd files, except for the targetport value
(he and I are using different desktops)
4.My connection fails. Hangs at "Making connection to xxx.xxx.xxx.xxx:x"
(where: xxx.xxx.xxx.xxx:x is the IP and VNC server instance numbers.)
5. I can connect to my VNC desktop through the internal network
without zebedee.
6. I can connect to my VNC desktop from home as well, without
using zebedee. Of course, before the zebedee test I disconnect.
Since we're coming in through my firewall at work on the same port, it can't be a
problem here. Since he's not on during the test (as verified by the log file) it can't
be "one instance of zebedee on a given port number will only support one
connection at a time." Since I can take my linksys router out of the equation by
direct-connecting the Win98 machine to the cable modem, repeat the test and get
the same result it can't be the linksys router. That only leaves the Roadrunner
"2-way" firewall.
Unless I missed something?
- John
---------------------------------------------------------------------
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
---------------------------------------------------------------------
