Date: Sun, 26 Oct 2003 16:34:28 -0600 From: "Charles Howse" <chowse@charter.net> To: "'Matthew Seaman'" <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: RE: Website up, then down, then up, etc. Message-ID: <000701c39c11$51c30be0$04fea8c0@moe>
next in thread | raw e-mail | index | archive | help
> > > > It certainly is perplexing. > > =20 > > > It is, isn't it? > >=20 > > Yes. I've had similar impossible problems in the past. One time it > > turned out to be a broken network cable, and the other time it was > > just my inability to fathom the somewhat obscure way a particular > > device implemented packet filtering. Once you know what the answer > > is, you'll wonder how it took you so long to realise something so > > obvious... >=20 > Been there, done that, got the T-shirt. :-) > I'm currently installing Apache2 on larry, the secondary FBSD=20 > machine to see if it works from there. > That should give me a clue, and won't hurt anything at all. Well, it's working now, but I don't know why. :-0 I unplugged the Cable Modem and Router overnight while I was at work. When I got home from work this morning, I installed Apache2 on larry, and configured the router to forward to larry on port 80. No joy. I reset all the router options to the defaults, and set up the port forwarding. No joy. Later, I decided to try and bypass the router by connecting curly (the original webserver) directly to the Cable Modem. I set curly for DHCP and rebooted, but it couldn't get an IP address (I probably didn't configure it right), so I set it back the way it was originally, and rebooted. Now it's working. 22:30 UTC.=20 Mother used to tell me, "Stop stomping around in the kitchen! I'm baking a cake, and it will fall." I'm going to walk very softly for a while.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000701c39c11$51c30be0$04fea8c0>