Date: Sat, 30 Oct 2004 00:48:38 -0600 From: Danny MacMillan <flowers@users.sourceforge.net> To: Clay <cculver@darkness-is.com> Cc: freebsd-questions@freebsd.org Subject: Re: Apache 2.0.52 help Message-ID: <20041030064838.GA1323@procyon.nekulturny.org> In-Reply-To: <20041030053323.870E543D49@mx1.FreeBSD.org> References: <1099113697.18749.329.camel@aaron.proficuous.com> <20041030053323.870E543D49@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 29, 2004 at 11:33:12PM -0600, Clay wrote: > It is not a DSL Router/Modem, just a straight old school ADSL > modem. I have three static IP addresses. One is being used for the > current web server, one is on the machine I am typing this on, and > the third is being used for this server for testing. You know, one thing that occurs to me is: are you obtaining your IP addresses from (your ISP's) DHCP server? If not, are you sure you are giving your new FreeBSD web server the right address? If the address you are using is incorrect, it's quite possible that the machine you are (successfully) pinging isn't the FreeBSD machine, just another unrelated host that responds to ping, as most hosts do, but doesn't have a web server running. If your machines are connected to the ADSL modem via a switch (which is how it sounds like you have things set up), the FreeBSD web server would still see and respond to the traffic addressed to its (incorrect) IP from your two other machines. I can think of two ways to test this: One, ping the host from the external non-working machine and monitor the FreeBSD machine to see if it is being pinged. I'm sure there's a way to do that, I just don't know what it is :) The other is to temporarily switch IP addresses with one of your other known working machines and see if you can access the web server via that address. -- Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041030064838.GA1323>