Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: error (nike.apache.org: local policy)
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="=_7b269e4a772ecb00f7a63cfe7bd8ec2c"
Date: Thu, 25 Jul 2013 03:58:38 -0400
From: "Michael D. Wood" <mike@itsecuritypros.org>
To: <users@httpd.apache.org>
In-Reply-To: <dd35c739-c2c0-4847-abe1-1eee4b8150a7@me.com>
References: <dd35c739-c2c0-4847-abe1-1eee4b8150a7@me.com>
Message-ID: <0d87a6f9439b94cec4115e2315135dc5@itsecuritypros.org>
User-Agent: Roundcube Webmail/0.8-rc
Subject: Re: [users@httpd] Router change issue

--=_7b269e4a772ecb00f7a63cfe7bd8ec2c
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=UTF-8

 
The new wireless router is configured the same way as your old
router was? As in, the same network configuration and I'm assuming the
server you have Apache running on has a static ip in the same network?


Not much that has to change - port forward to your server running
Apache. 

What are you getting when trying to access the site?
Connection timed out, just doesn't connect at all? 

On 07/24/2013 05:02
PM, James Coyle wrote: 

> I installed a new wireless router last night
from Comcast. Previously I had been using an Apple Airport Extreme as a
router along with a regular cable modem. I have duplicated the IP scheme
on this new router and have opened up the appropriate port so that
Apache can serve up my web site, but so far I have had no luck in
getting the pages to display. 
> 
> As I said, I've confirmed that the
correct port for my web hop via DYNDns is open (port 8102) and it is
mapped to my internal IP address. I have not changed my Apache config
file or anything else. 
> 
> The only thing I can think of here is that
Apache is confused by the change in hardware since both the Airport
Extreme and the new Comcast wireless router are/were using the same
10.0.0.x range of addresses. 
> 
> My old Airport is now in bridge mode
and is not acting as a router. 
> 
> I am reluctant to call Comcast,
first of all because they are Comcast, and secondly because they are now
pushing a higher level of paid support that I'm not interested in. I'd
appreciate any help anyone could provide. Thanks.

 
--=_7b269e4a772ecb00f7a63cfe7bd8ec2c
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style=3D'font-family: Verdana,Geneva,sans-serif'>
<p>The new wireless router is configured the same way as your old router wa=
s?&nbsp; As in, the same network configuration and I'm assuming the server =
you have Apache running on has a static ip in the same network?</p>
<p>Not much that has to change - port forward to your server running Apache=
=2E</p>
<p><br />What are you getting when trying to access the site?&nbsp; Connect=
ion timed out, just doesn't connect at all?</p>
<p>On 07/24/2013 05:02 PM, James Coyle wrote:</p>
<blockquote type=3D"cite" style=3D"padding-left:5px; border-left:#1010ff 2p=
x solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignore=
d --><!-- meta ignored -->
<div>I installed a new wireless&nbsp;router last night from Comcast. Previo=
usly I had been using an Apple Airport Extreme as a router along with a reg=
ular&nbsp;cable modem. I have duplicated the IP scheme on this new router a=
nd have opened up the appropriate port so that Apache can serve up my web s=
ite, but so far I have&nbsp;had no luck in getting the pages to display.</d=
iv>
<div>&nbsp;</div>
<div>As I said, I've confirmed that the correct port for my web hop via DYN=
Dns is open&nbsp;(port 8102) and it is mapped to my internal IP address. I =
have not changed my Apache config file or anything else.</div>
<div>&nbsp;</div>
<div>The only thing I can think of here is that Apache is confused by the c=
hange in hardware since both the Airport Extreme and the new Comcast wirele=
ss router are/were using the same 10.0.0.x range of addresses.</div>
<div>&nbsp;</div>
<div>My old&nbsp;Airport is now in bridge mode and is not acting as a route=
r.&nbsp;&nbsp;</div>
<div>&nbsp;</div>
<div>I am reluctant to call Comcast, first of all because they are Comcast,=
 and secondly because they are now pushing a higher level of paid support t=
hat I'm not interested in.&nbsp; I'd appreciate any help anyone could provi=
de. Thanks.</div>
</blockquote>
<div>&nbsp;</div>
</body></html>

--=_7b269e4a772ecb00f7a63cfe7bd8ec2c--