[users@httpd] Intermittent access to web address

2011-10-25 Thread Webmaster Bill

This is my first try at running a web site from a spare computer at home. I
am having some problems and
would appreciate some help. Please give your suggestions in a detailed
manner as I am unfamilar with most of
the terminology used.
My main problem is that after installing Apache 2.2.21 as a service on my
Windows7 o/s computer it has trouble
presenting the web page. It will work for a while then I start getting
connection time outs saying the web site is not
responding. This will probably take up a lot of space but I will try to list
all the info about my system and the settings
I have in apache.
Computer: Windows 7 O/S - AMD Athlon 64 X2 processor - 4600+ - 2.4 GHZ - 2GB
RAM

DYNEX 4 PORT 10/100 Mbs Ethernet Router

Ubee D3.0 Comcast Modem


Apache http server ver 2.2.21

Changes I made in httpd.conf file:

# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses. #
#Listen 12.34.56.78:80
Listen 76.18.232.237:80


# ServerName gives the name and port that the server uses to identify 
itself.

# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup. #
# If your host doesn't have a registered DNS name, enter its IP address 
here.

#
ServerName www.thepictureshow.net:80



Error Log after installing Apache:

Starting the Apache2.2 service The Apache2.2 service is running.
rmine the server's fully qualified domain name, using 192.168.1.102 for 
ServerName
[Tue Oct 25 14:16:57 2011] [notice] Apache/2.2.21 (Win32) configured - 
resuming normal operations
[Tue Oct 25 14:16:57 2011] [notice] Server built: Sep   9 2011 10:26:10 [Tue 
Oct 25 14:16:57 2011] [notice] Parent: Created child process 1380 httpd.exe: 
Could not reliably determine the server's fully qualified domain name, using 
192.168.1.102 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain 
name, using 192.168.1.102 for ServerName [Tue Oct 25 14:16:58 2011] [notice] 
Child 1380: Child process is running

[Tue Oct 25 14:16:58 2011] [notice] Child 1380: Acquired the start mutex.
[Tue Oct 25 14:16:58 2011] [notice] Child 1380: Starting 64 worker threads.
[Tue Oct 25 14:16:58 2011] [notice]Child 1380: Starting thread to  listen on 
port 80.



install log after installing apache:

installing Apache HTTP 2.0 server with DomainName = thepictureshow.net 
ServerName = www.thepictureshow.net ServerAdmin = webmasterb...@comcast.net

ServerPort = 80 ServerSslPort = 80
ServerRoot = C:/Program Files/Apache software Foundation/Apache2.2 Rewrote 
C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-autoi ndex.conf.i n to 
C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-autoi ndex.conf 
Successfully removed C:\Program Files\Apache Software Foundati 
on\Apache2.2\conf\ori gi nal\extra\httpd-autoi ndex.conf.i n Rewrote 
C:/Program Files/Apache Software
Foundation/Apache2.2/conf/original/extra/httpd-vhosts.conf.in to C:/Program 
Files/Apache Software
Foundation/Apache2.2/conf/original/extra/httpd-vhosts.conf Successfully 
removed C:\Program Files\Apache Software Foundati on\Apache2.2\conf\ori gi 
nal\extra\httpd-vhosts.conf.i n Rewrote C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-default.conf.i n to 
C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-default.conf Successfully 
removed C:\Program Files\Apache Software Foundati on\Apache2.2\conf\ori gi 
nal\extra\httpd-default.conf.i n Rewrote C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/origi nal/extra/httpd-manual.conf.i n to 
C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-manual.conf Successfully 
removed C:\Program Files\Apache Software Foundati on\Apache2.2\conf\origi 
nal\extra\httpd-manual.conf.i n Rewrote C:/Program Files/Apache software 
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-mpm.conf.i n
to C:/Program Files/Apache Software Foundati on/Apache2.2/conf/ori gi 
nal/extra/httpd-mpm.conf Successfully removed C:\Program Files\Apache 
Software Foundati on\Apache2.2\conf\ori gi nal\extra\httpd-mpm.conf.i n 
Rewrote C:/Program Files/Apache Software Foundati on/Apache2.2/conf/ori gi 
nal/extra/httpd-i nfo.conf.i n

to C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-i nfo.conf Successfully 
removed C:\Program Files\Apache Software Foundation\Apache2.2\conf\ori gi 
nal\extra\httpd-i nfo.conf.i n Rewrote C:/Program Files/Apache Software 
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-dav.conf.i n to C:/Program 
Files/Apache Software Foundation/Apache2.2/conf/ori gi 
nal/extra/httpd-dav.conf Successfully removed C:\Program Files\Apache 
Software Foundati on\Apache2.2\conf\ori gi nal\extra\httpd-dav.conf.i n 
Rewrote C:/Program Files/Apache Software
Foundati on/Apache2.2/conf/ori gi nal/extra/httpd-1anguages.conf.i n to 

Re: [users@httpd] Intermittent access to web address

2011-10-25 Thread Yehuda Katz
My message was caught by the list's spam filter the first time around.
Let's try again...

 On Tue, Oct 25, 2011 at 10:14 PM, Webmaster Bill
 wrote:
>
> This is my first try at running a web site from a spare computer at home.

You should make sure that this is not against the terms of service of
your provider (in this case, Comcast,
http://go.ymkatz.net/comcast-net-aup).

To get right to your problem:

>
> Changes I made in httpd.conf file:
>
> # Change this to Listen on specific IP addresses as shown below to
> # prevent Apache from glomming onto all bound IP addresses. #
> #Listen 12.34.56.78:80
> Listen 76.18.232.237:80
>
>
> # ServerName gives the name and port that the server uses to identify itself.
> # This can often be determined automatically, but we recommend you specify
> # it explicitly to prevent problems during startup. #
> # If your host doesn't have a registered DNS name, enter its IP address here.
> #
> ServerName www.thepictureshow.net:80

You need to set Apache to listen on the computer's local address, then
have your router forward the traffic from the public (comcast owned)
network to your internal network.
You will have another problem with that setup, since it appears that
your server does not have a static IP address.
In the error log that you supplied, your server has the address
192.168.1.102, which is in the address range usually assigned
automatically by your router.
If the computer does not have a fixed IP address, it is not possible
for your router to forward the traffic from the public network to your
private network.

- Y

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] Intermittent access to web address

2011-10-25 Thread William A. Rowe Jr.
On 10/25/2011 9:36 PM, Yehuda Katz wrote:
> In the error log that you supplied, your server has the address
> 192.168.1.102, which is in the address range usually assigned
> automatically by your router.
> If the computer does not have a fixed IP address, it is not possible
> for your router to forward the traffic from the public network to your
> private network.

With most routers, you can pin a specific MAC address to a specific reservation
even with DHCP.

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] Intermittent access to web address

2011-10-25 Thread Webmaster Bill

Forgot to mention that I have  a DNS service with a company called NO-IP.
They supply a static address of 76.18.232.237 for the web address.

"Wild" Bill Miller
Swampmaster

--
From: "Yehuda Katz" 
Sent: Tuesday, October 25, 2011 10:36 PM
To: 
Subject: Re: [users@httpd] Intermittent access to web address


My message was caught by the list's spam filter the first time around.
Let's try again...

On Tue, Oct 25, 2011 at 10:14 PM, Webmaster Bill
 wrote:


This is my first try at running a web site from a spare computer at home.


You should make sure that this is not against the terms of service of
your provider (in this case, Comcast,
http://go.ymkatz.net/comcast-net-aup).

To get right to your problem:



Changes I made in httpd.conf file:

# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses. #
#Listen 12.34.56.78:80
Listen 76.18.232.237:80


# ServerName gives the name and port that the server uses to identify
itself.
# This can often be determined automatically, but we recommend you
specify
# it explicitly to prevent problems during startup. #
# If your host doesn't have a registered DNS name, enter its IP address
here.
#
ServerName www.thepictureshow.net:80


You need to set Apache to listen on the computer's local address, then
have your router forward the traffic from the public (comcast owned)
network to your internal network.
You will have another problem with that setup, since it appears that
your server does not have a static IP address.
In the error log that you supplied, your server has the address
192.168.1.102, which is in the address range usually assigned
automatically by your router.
If the computer does not have a fixed IP address, it is not possible
for your router to forward the traffic from the public network to your
private network.

- Y

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
  "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org





-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
  "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] Intermittent access to web address

2011-10-25 Thread Steve Swift
When you start to get "not responding", are you testing from inside your
192.168.*.* network, or from beyond your router?

If you are testing from inside your network, are you fetching from
192.168.1.102 or from 76.18.232.237?
If the latter, then you should check your router to see if it allows such
"triangle connections", from inside your network, to the router, and back in
to your network. Mine (ZyXEL P660) initially blocked such indirect
connections (it throws work onto the router, to no purpose)

You might do better allocating your webserver system a fixed IP address
within your home network. Mine is on 192.168.1.2 - the router being
192.168.1.1


On 26 October 2011 03:14, Webmaster Bill  wrote:

> It will work for a while then I start getting
> connection time outs saying the web site is not
> responding.
>

-- 
Steve Swift
http://www.swiftys.org.uk


Re: [users@httpd] Intermittent access to web address

2011-10-26 Thread Webmaster Bill
I am testing from another computer on my home network but a friend a few miles 
away is testing the web address also and he encounters the same problems
. 
"Wild" Bill Miller
Swampmaster


From: Steve Swift 
Sent: Wednesday, October 26, 2011 2:12 AM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] Intermittent access to web address


When you start to get "not responding", are you testing from inside your 
192.168.*.* network, or from beyond your router?  


If you are testing from inside your network, are you fetching from 
192.168.1.102 or from 76.18.232.237?
If the latter, then you should check your router to see if it allows such 
"triangle connections", from inside your network, to the router, and back in to 
your network. Mine (ZyXEL P660) initially blocked such indirect connections (it 
throws work onto the router, to no purpose) 


You might do better allocating your webserver system a fixed IP address within 
your home network. Mine is on 192.168.1.2 - the router being 192.168.1.1



On 26 October 2011 03:14, Webmaster Bill  wrote:

  It will work for a while then I start getting
  connection time outs saying the web site is not
  responding.



-- 
Steve Swift
http://www.swiftys.org.uk


Re: [users@httpd] Intermittent access to web address

2011-10-26 Thread J.Lance Wilkinson

Webmaster Bill wrote:
*/I am testing from another computer on my home network but a friend a 
few miles away is testing the web address also and /**/he encounters the 
same problems/*


Another thing to consider is your ISP (COMCAST,  I understand from
an earlier post; same as mine) likely has terms in their service
contract which PROHIBIT you from running your own server visible thru
their network.  I know that it's explicitly prohibited in MY
(residential) terms of service with them.   Thus they could be BLOCKING
outside, including your friend's, access to you.   Read your terms of
service with them before spending too much time debugging things.

--
J.Lance Wilkinson ("Lance")   InterNet: lance.wilkin...@psu.edu
Systems Design Specialist - LeadPhone: (814) 865-4870
Digital Library TechnologiesFAX:   (814) 863-3560
E3 Paterno Library
Penn State University
University Park, PA 16802

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
  "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org