They may have blocked port 80.  Can you have your webserver respond on, say,
port 81 and see what happens.  If you are suddenly able to see the web-page,
then it is likely that port 80 is blocked.  While you're at it, you might
check ports 25, 110, 21 for ftp, smtp &pop3.

> -----Original Message-----
> From: Eric Rossiter [mailto:rossiter@discoverynet.com]
> Sent: Tuesday, January 23, 2001 12:30 PM
> To: Brian Kelsay; kclug@kclug.org
> Subject: Re: IPMASQ on the @home network......
> 
> 
> Actually, I'd like to figure out what's wrong with the 
> gatekeeper script I
> have in place now.....
> Can ping out from the Win machine , but no access on port 80 
> (no web pages
> come in)....I was just wondering if Comcast had found a way 
> to block it.....
> 
> I can include the script later if anyone would like to cast 
> an eyeball on it
> to see if I have erred.......
> 
> thanks
> 
> E
> ----- Original Message -----
> From: Brian Kelsay <bkelsay@askpioneer.com>
> To: <kclug@kclug.org>
> Sent: Tuesday, January 23, 2001 12:05 PM
> Subject: RE: IPMASQ on the @home network......
> 
> 
> > Yes, but I run the Freesco router distro to achieve that.  
> I didn't know
> all
> > the ins and outs of text config files and I wanted to get the stupid
> > firewall running so I could connect multiple PCs to the 
> net.  You can get
> > FreeSCO at www.freesco.org or you can use the LRP found at
> > www.linuxrouter.org if you know how to set the stuff up.  
> Luckily, for me,
> > once I learn more about router and firewall rules, FreeSCO 
> allows me to
> add
> > rules and add to tables.
> >
> > > -----Original Message-----
> > > From: Eric Rossiter [mailto:rossiter@discoverynet.com]
> > > Sent: Tuesday, January 23, 2001 11:34 AM
> > > To: kclug@kclug.org
> > > Subject: IPMASQ on the @home network......
> > >
> > >
> > > Hi pholks,
> > >
> > > Has anyone gotten IPMASQ to work on the @home network (Comcast) in
> > > Independence?
> > >
> > > Thanks,
> > >
> > > ER
> > >
> >
> >
> majordomo@kclug.org
>