On Fri, 26 Jan 2001 Charles Hines wrote:

> Sorry, I haven't been paying a lot of attention to this thread, so I apologize
> if I ask/suggest something that's already been discussed.

You're in the first response group.

> I've used Zebedee over my RoadRunner connection ("two-way" as you describe it)
> with no problems.  But for reasons of getting through various (non RoadRunner)
> firewalls involved I had to change the default port it uses.  Have you tried a
> couple of random ports to see if they aren't just blocking the default Zebedee
> port for some reason?

I've tried about 50 ports.

Let me be a bit more thorough at this point:
     1. I'm setting this up at my home office for remote admin work to the work office.
     2. I've got more than one PC in the home office, so to allow them all access to
         the 'net simultaneously, I've hooked up a Cable/DSL router.  That's the MAC
         address that RoadRunner authorizes.
     3. One PC is Win95, the other I'm working with is Win98.
     4. Both will connect through the router to my VNC server at work (Linux) w/o
         zebedee just fine.  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.
     5. I then break the connection and try to reconnect via zebedee.  No joy.
     6. Thinking the router might be a problem, I asked roadrunner to allow for
         a different MAC address to be authorized... and they did.  The Win98
         machine will surf the web when direct-connected to the cable modem
         (which takes the router out of the equation here), but will still not connect
         to the linux box via zebedee.  It will continue to connect w/o zebedee.

All this tells me that it's not my PC's, or the Cable/DSL router, but must be something
at the firewall at RoadRunner.  Too, other users following my setup instructions 
(including
that one user using the RoadRunner one-way product) are connecting via zebedee no
problem.  One other user of RoadRunners' two-way product and a user of the Qwest DSL
product cannot get in.

Hmmm.  I just thought of another question.  I wonder if (since I'm running about 16 
VNC server
sessions on linux), I have to create 16 instances of the zebedee server, all listening 
on
different ports? (probably)  Or will 16 instances of zebedee all on one port work? (I 
doubt it)
Or will one instance of zebedee support 16 connection? (I doubt this, too).  Time for 
some
testing...

> Seems like a really stupid policy as there are (as we all know, obviously)
> very good reasons for using secure tunnels over the Internet for certain
> things.  Did they give you any reasoning for this attitude?

They did not.

> Ridiculous.  I can't wait until they get a little more widespread competition
> from DSL, satellite, etc.  Knock them down a peg or two (hopefully price wise
> as well). :)  

I've already posed a few questions along these lines to the support group at
Starband.

> They can't be blocking every port that you might want to use since the more
> they block the less useful they become to their customers (eg: online games
> use a bunch of different ports to do their connections).  You know that they
> let port 80 through for web access, at the very least, so you could try using
> that for zebedee communications (as a test case if not practical for actual
> usage).

> Chuck

> - -- 
> Charles K. Hines   <[EMAIL PROTECTED]>   <[EMAIL PROTECTED]>
> Principal Scientist at ReQuest Technologies Inc   (http://www.ReQuestTech.com/)
> Martial Arts Instructor [Modern Arnis and Balintawak Escrima]

>          "Go back to sleep, Chuck.  You're just havin' a nightmare
>              -- of course, we ARE still in Hell." (Gary Larson)

And guess what else I just found out while typing this... one of the guys managing
the firewall at work thinks there might be an issue with the firewall here at work, 
too.
I don't know how I'll feel if this turns out to be the issue.  Relieved, or stupid. :-(

 - 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
---------------------------------------------------------------------

Reply via email to