the firewall and gallery are on the same machine re: clark connect 2.0 the firewall is allowing incoming connections on port 80 the firewall is also forwarding port 80 to 192.168.1.1 and 68.144.149.3 which is the same machine.
J ----- Original Message ----- From: "Nick W" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 5:17 PM Subject: Re: (clug-talk) isp blocking ports Sounds like youre behind a router, you need to forward port 80 to your web-serving computer's IP. Should be an easy fix... NOOB NOTE: The reason this works is because when a computer requests a web page, it does so on port 80 [by default]. If the host [the web-server] is behind a router, typically any un-explicitly requested inbound traffic is blocked by the router. Port forwarding tells the router not to drop requests for a specified port, but to send them to a specific computer. On October 13, 2003 03:42 pm, Jon Copeland wrote: > im a bit of a noob, how would the port forwarding of http traffic allow me > to circumvent the problem im having. maybe i should give a bit of > background on the pc in question. > > Pentium 200 running clark connect 2.0 home edition (which somebody gave me > at the meeting). > CC-Gallery comes packaged with clark connect http://gallery.menalto.com/ , > hosting the site at http://home.jon.za.net/ which is simply a dns redirect > to my ip address 68.144.149.3 > > anybody on the lan can view the gallery but nobody in the outside world can > view it. > > i posted a technical question here which explains the problem in greater > detail > http://www.clarkconnect.com/forums/showflat.php?Cat=&Board=netmanage&Number >=42287&page=0&view=expanded&sb=5&o=&fpart=1#Post42299 > > anyway i am up until 5:30 this morning trying to fix it, needless to say im > exhausted. > > jon > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, October 13, 2003 3:22 PM > Subject: Re: (clug-talk) isp blocking ports > > > no port blocking? > > Nope, they don't activily block ports.... neither does Telus for that > matter. > > > i found this piece of info on the 'business' side of the shaw website > > "Please note The following services are not allowed to be run on Shaw > > provided IP Addresses: http, ftp, nntp, pop and smtp" > > i wonder if it applies to residential customers too? > > Yes, you can only provide http, ftp, nttp, pop, and smtp services if you > have a business package with servers allowed.... legally that is but there > is no technical reason why you can't. > > > jon > > > > ----- Original Message ----- > > From: "todd almond" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, October 13, 2003 10:56 AM > > Subject: Re: (clug-talk) isp blocking ports > > > > > > Nope, no port blocking. Except for a brief period when the blaster worm > > was out, port 135 was shut-off. > > (I'm a TSR there...) > > > > Jon Copeland wrote: > >>does anyone know if shaw blocks, among other things, port 80? > >>and if they are is there a way around this? im looking at hosting a LOW > >>TRAFFIC picture gallery for my family around the world and i'd like to > >>accomplish this using my existing infrastructure and not incur any > >>additional costs. > >> > >>jon > > Cheers, > > Trevor -- Nick W ([EMAIL PROTECTED]) Registered Linux User #324288 (http://counter.li.org) MSN Messenger: [EMAIL PROTECTED] Yahoo: foolish_gambit ICQ: 303276221
