Apache 2.0.52 and Windows XP Pro SP2

I'm running a system with WinXP SP2 and people cannot connect to the
webserver. Everything seems to be running fine (http://localhost works,
and so does 127.0.0.1) on the Apache side of things but for some reason
people can't connect to the server. I used to have WinXP SP1 and I had
no problems whatsoever. Since the upgrade to SP2 I can't seem to get
this thing working. The Windows firewall is disabled and it has been
disabled since the first boot and I know its not the problem because
I'm also running an ftp server and that works perfectly fine. Any ideas?

bump

On 13 Jan 2005, dradano@gmail.com wrote in
news:1105612646.565688.204930@f14g2000cwb.googlegr oups.com:

> I'm running a system with WinXP SP2 and people cannot connect to
> the webserver. Everything seems to be running fine
> (http://localhost works, and so does 127.0.0.1) on the Apache side
> of things but for some reason people can't connect to the server.
> I used to have WinXP SP1 and I had no problems whatsoever. Since
> the upgrade to SP2 I can't seem to get this thing working. The
> Windows firewall is disabled and it has been disabled since the
> first boot and I know its not the problem because I'm also running
> an ftp server and that works perfectly fine. Any ideas?

I'm sorry that I don't know the answer to your question. I keep hearing
about people having trouble running Apache 2 on Windows XP, so
yesterday I installed it myself on that system (XP Pro SP2). It worked
right away, right out of the box, no tweaking needed. I could connect
to it from the local machine as localhost and IP address. I could
connect to it from across the LAN by IP address. I could connect to it
from the internet by named URL. I had to forward the port in my router
to that machine, of course. The Microsoft firewall was enabled, I just
had to tell it to allow Apache.

Maybe your ISP is blocking port 80? What happens if you run Apache on
another port?

I apologize for bumping my post, but it is in fact my ISP. The crappy
thing about it is I've been a customer with this ISP for seven years
and only now (2005) did they decide to block my port 80. As you may
guess I'm quite mad.

I would like to thank you for your reply and the test that you ran. I
know now that it'll work right out of the box, as soon as my ISP gets
their crap together. Thank you.

On 17 Jan 2005, dradano@gmail.com wrote in
news:1105990333.257734.228570@c13g2000cwb.googlegr oups.com:

> I apologize for bumping my post, but it is in fact my ISP. The crappy
> thing about it is I've been a customer with this ISP for seven years
> and only now (2005) did they decide to block my port 80. As you may
> guess I'm quite mad.
>
> I would like to thank you for your reply and the test that you ran. I
> know now that it'll work right out of the box, as soon as my ISP gets
> their crap together. Thank you.

If I were you, I'd assume that if the ISP has blocked port 80, they
plan to do it permanently. The solution it to just run it on another
port, and be sure to include that when you pass out the URL, a la
<http://my.home.server:8081/>. That's what I do.