I have two identical boxes, one for development and one for
production.  The two have identical configuration files, software,
and compile time options.

When I went to put Apache2 on the production box, I had no
errors when I compiled, nor did I have a problem starting it up.
There is nothing in the error_log or syslog.

But, no browser, whether on the production box itself or on the
LAN or across the Internet, can interact with the web service at
all.  The firewall is down, the port is very much open, and it is
using a configuration identical to the dev box.

Since the dev box works without a hitch and the production box
is essentially identical, I am not sure why I cannot access the
service through a web browser.  Considering how I can telnet to
the production box on port 80 and manually request pages and
have it work perfectly, I'm even more confused.

Here's a screen capture to detail the problem a bit more:
http://koa.la/apache2.jpg

I'm thinking it's something really trivial that I'm overlooking, but
I'm stumped.  Any thoughts?

[ Post a follow-up to this message ]

sounds like a dns issue ? or browser not liking IPV6 ?

have you tried http://ip.address.of.system/

?/?

"Josh" <mykoala@gmail.com> wrote in message =
news:369addf7.0409150500.12dcc15a@posting.google.com...
> I have two identical boxes, one for development and one for
> production.  The two have identical configuration files, software,
> and compile time options.
>=20
> When I went to put Apache2 on the production box, I had no
> errors when I compiled, nor did I have a problem starting it up.
> There is nothing in the error_log or syslog.
>=20
> But, no browser, whether on the production box itself or on the
> LAN or across the Internet, can interact with the web service at
> all.  The firewall is down, the port is very much open, and it is
> using a configuration identical to the dev box.
>=20
> Since the dev box works without a hitch and the production box
> is essentially identical, I am not sure why I cannot access the
> service through a web browser.  Considering how I can telnet to
> the production box on port 80 and manually request pages and
> have it work perfectly, I'm even more confused.
>=20
> Here's a screen capture to detail the problem a bit more:
>                  http://koa.la/apache2.jpg
>=20
> I'm thinking it's something really trivial that I'm overlooking, but
> I'm stumped.  Any thoughts?

[ Post a follow-up to this message ]

quick search on google and results seem to show browser issues
"Josh" <mykoala@gmail.com> wrote in message =
news:369addf7.0409150500.12dcc15a@posting.google.com...
> I have two identical boxes, one for development and one for
> production.  The two have identical configuration files, software,
> and compile time options.
>=20
> When I went to put Apache2 on the production box, I had no
> errors when I compiled, nor did I have a problem starting it up.
> There is nothing in the error_log or syslog.
>=20
> But, no browser, whether on the production box itself or on the
> LAN or across the Internet, can interact with the web service at
> all.  The firewall is down, the port is very much open, and it is
> using a configuration identical to the dev box.
>=20
> Since the dev box works without a hitch and the production box
> is essentially identical, I am not sure why I cannot access the
> service through a web browser.  Considering how I can telnet to
> the production box on port 80 and manually request pages and
> have it work perfectly, I'm even more confused.
>=20
> Here's a screen capture to detail the problem a bit more:
>                  http://koa.la/apache2.jpg
>=20
> I'm thinking it's something really trivial that I'm overlooking, but
> I'm stumped.  Any thoughts?

[ Post a follow-up to this message ]

The browser pictured isn't the problem - the same thing happens in Firefox,
IE, Camino, and Opera.  Strangely, it wors fine in Mozilla.  This is for bot
h PC
and mac versions of the browsers.

As far as IPv6 goes, that's what I originally thought, but I've bound it to 
an IPv4
address and even have no special considerations made in the conf for IPv6.
Still no success.

Totally stumped..

[ Post a follow-up to this message ]