Web Servers on Windows - Apache HTTP Server 2.2 on Windows XP

This is Interesting: Free IT Magazines  
Home > Archive > Web Servers on Windows > May 2006 > Apache HTTP Server 2.2 on Windows XP





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Apache HTTP Server 2.2 on Windows XP
Fetter

2006-05-05, 1:15 pm

I have an always on DSL connection with Windows XP Pro. I have
installed Apache HTTP Server 2.2. After registering at www.dyndns.com
to get my own web site name I have all that linked together. I have
apache setup to go off of the dyndns.org and with my full server name
set up through there as well. When I type iit in on my computer it
works fine (of course). When I try it in IE on another computer in my
house that uses the DSL, it works. Anywhere outside of my house can't
see it. I have the config file set to listen to
fe#######.dyndns.org:80. After running a port scan it says it didn't
see anything running on port 80. I have windows firewall accepting
port 80. I also turned on port forwarding through my router. Is there
anything here that it looks like I am missing?

Desperate in Buffalo

Phil Frisbie, Jr.

2006-05-05, 1:15 pm

Fetter wrote:

> I have an always on DSL connection with Windows XP Pro. I have
> installed Apache HTTP Server 2.2. After registering at www.dyndns.com
> to get my own web site name I have all that linked together. I have
> apache setup to go off of the dyndns.org and with my full server name
> set up through there as well. When I type iit in on my computer it
> works fine (of course). When I try it in IE on another computer in my
> house that uses the DSL, it works. Anywhere outside of my house can't
> see it. I have the config file set to listen to
> fe#######.dyndns.org:80. After running a port scan it says it didn't
> see anything running on port 80. I have windows firewall accepting
> port 80. I also turned on port forwarding through my router. Is there
> anything here that it looks like I am missing?


It is common for ISPs to block port 80 incoming. Read your terms of service to
see if this is the case. If it is then your only choice may be to either pay a
higher monthly fee for business DSL, or perhaps they do not block on static IPs,
or switch ISPs.

--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com
Fetter

2006-05-05, 1:15 pm

It says they give 10mb for web page hosting but didn't see much on port
80 for what I looked at.

Anyone here use Verizon DSL and can host their own website?

Nil

2006-05-05, 7:15 pm

On 05 May 2006, "Fetter" <rob.fetterhoff@gmail.com> wrote in
news:1146850871.547720.80310@i40g2000cwc.googlegroups.com:

> It says they give 10mb for web page hosting but didn't see much on
> port 80 for what I looked at.


They are referring to running a web site from THEIR server, not from
yours.

Try running your server on a port other than 80.
Fetter

2006-05-06, 1:18 am

That's my problem. I'm not quite sure how. Do I just tell the server
to listen to a different port in the config file?

Fetter

2006-05-06, 1:18 am

I changed the listen to port 81... now on my local if I type the
webpage name with the ":81: after it it comes up (won't come up any
other way). IE on my computer downstairs sees it but AOL doesn't.
Just like before. I can't really test it further than that cause there
is no one online to ask to test it. Am I doing this right?

Fetter

2006-05-06, 1:18 am

Sorry... I meant to have quotes around the ":81"

Nil

2006-05-06, 1:14 pm

On 06 May 2006, "Fetter" <rob.fetterhoff@gmail.com> wrote in
news:1146894238.616004.73480@j73g2000cwa.googlegroups.com:

> I changed the listen to port 81... now on my local if I type the
> webpage name with the ":81: after it it comes up (won't come up
> any other way). IE on my computer downstairs sees it but AOL
> doesn't. Just like before. I can't really test it further than
> that cause there is no one online to ask to test it. Am I doing
> this right?


To make my server use port 8081, the Listen line in my httpd.conf file
is:

Listen 8081

(no IP address or host name)


and the ServerName directive line is:

ServerName myserver.mydomain.org:8081


to reach my server you would use a url like
<http://myserver,mydomain.org:8081/> or <http://123.456.77.9:8081/>.


What does AOL have to do with it? Do you mean that the AOL browser
doesn't see it? Or are you connecting to the internet through AOL?

Maybe your ISP (AOL?) is blocking port 81 as well as 80.

What did you use to do the port scan? Here's one site that will scan
the ports for you to test what ports are open:

https://www.grc.com/x/ne.dll?bh0bkyd2

Are you sure you have port forwarding set up correctly?
Fetter

2006-05-06, 1:14 pm

I just use IE to browse the internet... I have Verizon DSL. My
siblings have AOL installed on their computer and it can't see my
server. Although IE on their computer can. Any computer outside of my
house cannot see it at all.

I ran your port scan site. It couldn't find anything at any port that
it scanned when doing the Service ports probe. Everything was stealth.
What does that mean?

I'm almost positive I have port forwarding set up right on my router.
It's an option in the set up.

Nil

2006-05-06, 1:14 pm

On 06 May 2006, "Fetter" <rob.fetterhoff@gmail.com> wrote in
news:1146927126.337051.8860@j33g2000cwa.googlegroups.com:

> I ran your port scan site. It couldn't find anything at any port
> that it scanned when doing the Service ports probe. Everything
> was stealth.
> What does that mean?


I ran it myself a few minutes ago. There seems to be 3 possible
results.

- if the port is closed in my firewall, it's listed as "Stealth"

- if the port is open in my firewall, but the server is not running,
it's usually listed as "closed", but sometimes "stealth".

- if the port is open and the server is running, it's listed as "open"


It seems to me that either your ports are blocked by your ISP or your
router/firewall isn't set up correctly, or Windows firewall is blocking
things.

You might want to check out <http://www.portforward.com/> for advice on
how to work through the port forwarding issue.

Otherwise, I'm running out of ideas.
webwolf_3000

2006-05-07, 7:13 am

AOHELL needs the its own browser open in order for the connection to
work.

open AOL's browser and minimize it then open Internet Explorer, that
will probably work.
if it doesnt then you may need to set up the server in the hosts file
on all the computers.

C:\windows\system32\drivers\etc\hosts ( open hosts in notepad )

add the line/s

192.168.1.12 www.digitalwolf.org

where 192.168.1.12 is your servers LAN IP.
and www.digitalwolf.org is your fully qualified domain name.

for future reference, dont use AOL.
they are the absolute worst ISP money can buy..

Benedictum

2006-05-12, 7:13 pm

Go SBC or Comcast.

I use ports 8080 and 8085 / no-ip.com for DNS host. I also installed their
Dynamic Update. No problem.

"webwolf_3000" <webwolf_3000@msn.com> wrote in message
news:1147001527.767481.319620@i39g2000cwa.googlegroups.com...
> AOHELL needs the its own browser open in order for the connection to
> work.
>
> open AOL's browser and minimize it then open Internet Explorer, that
> will probably work.
> if it doesnt then you may need to set up the server in the hosts file
> on all the computers.
>
> C:\windows\system32\drivers\etc\hosts ( open hosts in notepad )
>
> add the line/s
>
> 192.168.1.12 www.digitalwolf.org
>
> where 192.168.1.12 is your servers LAN IP.
> and www.digitalwolf.org is your fully qualified domain name.
>
> for future reference, dont use AOL.
> they are the absolute worst ISP money can buy..
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com