Port 80 Firewall Settings

In article <20071010074957.37995a06 DeleteThis @oscar-sled.homeunix.net>,
malcolm_nospamlewis DeleteThis @bellsouth.net says...

....

> What router are you using? If you go to grc.com and do a port scan of
> your ip address, is port 80 open? If not your ISP may be blocking it?

Which is pretty common on residential (non-business) internet
connections.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
 >> Stay informed about: Port 80 Firewall Settings 

>>
> Hi
> What router are you using? If you go to grc.com and do a port scan of
> your ip address, is port 80 open? If not your ISP may be blocking it?
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
>

hmmm. That's interesting
I tried this GRC.com and initially the port was closed. When I opened the
router for configuration and changed the server IP to match the static IP is
and re ran this grc the port is now OPEN....HOWEVER, when I tried to start
Apache, I get an error: "make sock could not bind to address 0.0.0.0:80, no
listening sockets available".

Does this make sense to anyone?
 >> Stay informed about: Port 80 Firewall Settings 

> Hi
> So on page 26, you have ID #1 with service port http active, then the
> schedule set to always on and enabled, the server ip address should
> point to your internal ip address.
>
> Changed your ip?? Your internet facing ip is a static one set by your
> ISP eg 123.456.789.123 which points to your internal ip address eg
> 192.168.1.50 or whatever range you are using for your internal
> addressing.
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
> SLED 10.0 SP1 x86_64 Kernel 2.6.16.53-0.8-smp
> up 4:52, 2 users, load average: 0.33, 0.30, 0.22

Hi again:
Yes I have set (as you refer on Page 26 of Airlink Manual) ID 1 Port 80
enabled always on
that is now pointing to my internal IP address as determined by running c:\>
ipconfig /all For example:
ipaddress..................192.168.x.xxx

What I mean by "static ip" is that a website advising on port forwarding
suggested making a static IP on my computer (might resolve issues) by right-
clicking on my network connection and editing properties to reflect the data
acquired by running the c:/> ipconfig /all comand
I then hardcoded the various values into the internet protocol properties:



Having done all this Apache still gives the error "apache cannot bind to
addres 0.0.0.0:80, no listening sockets available".
 >> Stay informed about: Port 80 Firewall Settings 

jim wrote:
> I'm in trouble now.
> I disabled the DCHP and I cannot get back to the router to enable it
> Nothing works through the router - no internet.
> I had to unplug it and go direct to the net so I could post for help
> I read the Airlink manual and did everything it asked but unable to get any
> signal from the router
>
> What now?
>
>
Call support

--
DM davidm.DeleteThis@cia.com.au

'It would go against respecting principles and truth if you have to
respect and accept anything just because it is the other side's view.'
- Kim Jung Ill
 >> Stay informed about: Port 80 Firewall Settings 

I'm in trouble now.
I disabled the DCHP and I cannot get back to the router to enable it
Nothing works through the router - no internet.
I had to unplug it and go direct to the net so I could post for help
I read the Airlink manual and did everything it asked but unable to get any
signal from the router

What now?

>
> On the machine your running the apache server, set the 'static' ip
> address outside the range of any dhcp type addresses issued by the
> router. At the moment it your router may be sending out a full range.
> If it's the only pc on your lan, then disable dhcp from the router,
> else setup a range that exceeds the amount of pc's on the lan, plus 2
> for a few extras.
>
> Now see if the apache server starts and you can http://localhost and
> see if you get the "it works page", or the apache server test page. If
> you do have another pc on your lan, then try http://<static ip address>
>
> If all that works, then we can move forward.....
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
> SLED 10.0 SP1 x86_64 Kernel 2.6.16.53-0.8-smp
> up 5:57, 1 user, load average: 0.22, 0.17, 0.16
 >> Stay informed about: Port 80 Firewall Settings 

It's all okay now. I unplugged it for a good long time (overnight) and tried
it this morning -- is okay.
Not sure why it didn't reset the first time.

Now back to the drawing board.

"Malcolm" <malcolm_nospamlewis RemoveThis @bellsouth.net> wrote in message
news:20071011065335.19083401@oscar-sled.homeunix.net...
> On Thu, 11 Oct 2007 04:27:40 GMT
> "jim" <jim RemoveThis @pioneers.ca> wrote:
>
>> I'm in trouble now.
>> I disabled the DCHP and I cannot get back to the router to enable it
>> Nothing works through the router - no internet.
>> I had to unplug it and go direct to the net so I could post for help
>> I read the Airlink manual and did everything it asked but unable to
>> get any signal from the router
>>
>> What now?
>>
>> >
>> > On the machine your running the apache server, set the 'static' ip
>> > address outside the range of any dhcp type addresses issued by the
>> > router. At the moment it your router may be sending out a full
>> > range. If it's the only pc on your lan, then disable dhcp from the
>> > router, else setup a range that exceeds the amount of pc's on the
>> > lan, plus 2 for a few extras.
>> >
>> > Now see if the apache server starts and you can http://localhost and
>> > see if you get the "it works page", or the apache server test page.
>> > If you do have another pc on your lan, then try http://<static ip
>> > address>
>> >
>> > If all that works, then we can move forward.....
>> >
> Hi
> There is a button to reset to factory defaults.
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
> SLED 10.0 SP1 x86_64 Kernel 2.6.16.53-0.8-smp
> up 15:43, 1 user, load average: 0.10, 0.20, 0.14
 >> Stay informed about: Port 80 Firewall Settings 

Okay..feeling really dumb now.

I figured out why I was getting the error "cannot bind to 0.0.0.:80 Apache
was already running. There is no indication of this but it must start
automatically when I start the computer.

So, that it working fine.

So, is there a need to go back to what you suggested below, or can we move
forward to the next step to resolve this issue.

One poster suggested that my ISP may be blocking, but GRC.com says port 80
is OPEN



>> > On the machine your running the apache server, set the 'static' ip
>> > address outside the range of any dhcp type addresses issued by the
>> > router. At the moment it your router may be sending out a full
>> > range. If it's the only pc on your lan, then disable dhcp from the
>> > router, else setup a range that exceeds the amount of pc's on the
>> > lan, plus 2 for a few extras.
>> >
>> > Now see if the apache server starts and you can http://localhost and
>> > see if you get the "it works page", or the apache server test page.
>> > If you do have another pc on your lan, then try http://<static ip
>> > address>
>> >
>> > If all that works, then we can move forward.....
>> >
> Hi
> There is a button to reset to factory defaults.
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
> SLED 10.0 SP1 x86_64 Kernel 2.6.16.53-0.8-smp
> up 15:43, 1 user, load average: 0.10, 0.20, 0.14
 >> Stay informed about: Port 80 Firewall Settings 

By Golly I think he's (me) got it!
Not without the patient guidance of Malcom.

Hopefully I haven't cracked the champagne too soon, but I was able to access
my server through a VPN connection to my external IP address. I think that's
at least a step in the right direction (I hope).

Knock wood! I've asked a few friends to try it from where they are for
additional confirmation.

Whew! That was HARD.
 >> Stay informed about: Port 80 Firewall Settings 

"Allowing the port to accept traffic in your server firewall". AH -This is
the CRUX of my problem.

Currently the only way for me to test this, that I know of is to have an
external user attempt to see my server over the web by typing in my IP
(Which IP should they be using?). So far as I know no external users can see
my server over the web

Let me summarize (as this is getting confusing for me, so I can imagine how
it might look to someone else)

1. I used GRC and confirmed that Port 80 is open.
2. I set the static IP to 192.xxx.1.205 which is outside any DHCP range in
the router (they go 100 - 199)
3. I do occassionally have another computer on my network - I connect my
office laptop every so often. I can see the server from it when I type in
the internal IP, BUT CANNOT see it when I type in http://localhost
4. In CAN see local host with the PC that has Appache running on it and that
my server directory is located on (it shows the directory and few files i
have there when I set up appache config.
5. I cannot see anything with localhost on the other PC that I occassionally
have on the network (My office laptop), but I can see the server if I type
in the ip address 192.xxx.1.205
6. I have no idea how to set things up so that my server firewall will
accept traffic from the web.

Questions:
1. Is typing http://locahost on the other pc that doesn't have the server
stuff on it a way of testing if web traffic is being accepted through the
firewall?




"> Hi
> So you can see the server running on http://localhost ok?
>
> Do you have another pc on your internal network to check from?
>
> Have you allowed port 80 to accept traffic in your server firewall?
>
> If all above then you should be able to do the port forward rulle in
> your router and should all kick into life.
>
> If your apache server is working ok, then it really is a bit off topic
> for here. If you want to start a thread in a more appropriate newsgroup
> (tell me where) or an email feel free to do so just remove the
> nospam bit
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
> SLED 10.0 SP1 x86_64 Kernel 2.6.16.53-0.8-smp
> up 18:09, 2 users, load average: 0.37, 0.28, 0.14
 >> Stay informed about: Port 80 Firewall Settings 

Is my external IP address the same as my internal one? I have to assume NO
since you made special reference to it. So, what is it? OR should I say: how
do I determine what my external IP address is? Is it the one that comes up
on grc.com.
What is a dynamic IP address and how would I know I have that?

"Malcolm" <malcolm_nospamlewis.DeleteThis@bellsouth.net> wrote in message
news:20071011113706.3daff748@oscar-sled.homeunix.net...
> On Thu, 11 Oct 2007 15:45:32 GMT
> "Jim" <jimt.DeleteThis@pioneers.ca> wrote:
>
>> "> Hi
>> > So you can see the server running on http://localhost ok?
>> >
>> > Do you have another pc on your internal network to check from?
>> >
>> > Have you allowed port 80 to accept traffic in your server firewall?
>> >
>> > If all above then you should be able to do the port forward rulle in
>> > your router and should all kick into life.
>> >
>> > If your apache server is working ok, then it really is a bit off
>> > topic for here. If you want to start a thread in a more appropriate
>> > newsgroup (tell me where) or an email feel free to do so just
>> > remove the nospam bit
>
>
>> "Allowing the port to accept traffic in your server firewall". AH
>> -This is the CRUX of my problem.
>>
>> Currently the only way for me to test this, that I know of is to have
>> an external user attempt to see my server over the web by typing in
>> my IP (Which IP should they be using?). So far as I know no external
>> users can see my server over the web
>>
>> Let me summarize (as this is getting confusing for me, so I can
>> imagine how it might look to someone else)
>>
>> 1. I used GRC and confirmed that Port 80 is open.
> OK, this is good
>
>> 2. I set the static IP to 192.xxx.1.205 which is outside any DHCP
>> range in the router (they go 100 - 199)
> Excellent
>
>> 3. I do occassionally have another computer on my network - I
>> connect my office laptop every so often. I can see the server from it
>> when I type in the internal IP, BUT CANNOT see it when I type in
>> http://localhost
> This is correct unless you add a 'friendly' name in the machine you are
> try to connect from in your INTERNAL network you will need to use the
> ip address, unless you run a local dns where you could add this.
>
>>4. In CAN see local host with the PC that has
>> Appache running on it and that my server directory is located on (it
>> shows the directory and few files i have there when I set up appache
>> config.
> Good
>
>>5. I cannot see anything with localhost on the other PC that
>> I occassionally have on the network (My office laptop), but I can see
>> the server if I type in the ip address 192.xxx.1.205
> See 3
>
>> 6. I have no idea how to set things up so that my server firewall
>> will accept traffic from the web.
> If GRC is showing port 80 open, all is good.
>
>> Questions:
>> 1. Is typing http://locahost on the other pc that doesn't have the
>> server stuff on it a way of testing if web traffic is being accepted
>> through the firewall?
> No, you need to use the ip address, see 3, so if from an INTERNAL
> machine if it works, all is good.
>
> So, to test externally unless you have a domain name setup pointing to
> your EXTERNAL ip address, users need to use
> http://<your_EXTERNAL_ip_address> to connect.
>
> Have a look at http://www.dyndns.com/ if you have a dynamic
> EXTERNAL address
>
> --
> Cheers Malcolm °¿° (Linux Counter #276890)
> SLED 10.0 SP1 x86_64 Kernel 2.6.16.53-0.16-smp
> up 0:22, 1 user, load average: 0.45, 0.99, 1.01
 >> Stay informed about: Port 80 Firewall Settings