> > > > It certainly is perplexing.
> >
> > > It is, isn't it?
> >
> > 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 impl
> > > On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote:
>
> > > Hmmm... It's not the basic "look up the IP number" part as that's
> > > working just fine. You don't seem to be using their (dynDNS) web
> > > redirection service (ie. howse.homeunix.net resolves to
> 66.168.145.25
> >
On Sat, Oct 25, 2003 at 05:07:31PM -0500, Charles Howse wrote:
> > On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote:
> > Hmmm... It's not the basic "look up the IP number" part as that's
> > working just fine. You don't seem to be using their (dynDNS) web
> > redirection service (ie.
> On Sat, 25 Oct 2003 17:07:31 -0500
> "Charles Howse" <[EMAIL PROTECTED]> wrote:
>
> > Yes, the router has a web interface for configuration. It had been
> > set to forward requests on port 80 to the webserver on port
> 80. That
> > was working perfectly for over a year. I've now set it to
>
On Sat, 25 Oct 2003 17:07:31 -0500
"Charles Howse" <[EMAIL PROTECTED]> wrote:
> Yes, the router has a web interface for configuration. It had been
> set to forward requests on port 80 to the webserver on port 80. That
> was working perfectly for over a year. I've now set it to port 8080,
> in a
> On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote:
>
> > > That's good in one way: it means that your system is
> actually working
> > > perfectly well. Unfortunately it also implies that the problem is
> > > actually somewhere in the network downstream of you.
> Since it seems
>
On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote:
> > That's good in one way: it means that your system is actually working
> > perfectly well. Unfortunately it also implies that the problem is
> > actually somewhere in the network downstream of you. Since it seems
> > to affect all
> On Sat, Oct 25, 2003 at 10:58:53AM -0500, Charles Howse wrote:
> > I did change the listen address to 8080 in httpd.conf and
> in the port
> > forward on the router, and rebooted.
> > NOW IT IS WORKING! As of 10:42 CDT, which is 16:42 UTC.
> > http:/howse.homeunix.net:8080
> > Is there anything
On Sat, Oct 25, 2003 at 10:58:53AM -0500, Charles Howse wrote:
> I did change the listen address to 8080 in httpd.conf and in the port
> forward on the router, and rebooted.
> NOW IT IS WORKING! As of 10:42 CDT, which is 16:42 UTC.
> http:/howse.homeunix.net:8080
> Is there anything else to look at
How often do you reboot your router? My router flakes out every few
months and I need to reboot it.
On Oct 24, 2003, at 8:14 PM, Charles Howse wrote:
Hi,
For the past week or so I've been pulling my hair out trying to
diagnose
what's going on with my website.
Prior to that, everything was work
On Friday 24 October 2003 08:36 pm, Charles Howse wrote:
> > Hi Charles,
> >
> > --On Friday, October 24, 2003 08:40:09 PM -0500 Charles Howse
> >
> > <[EMAIL PROTECTED]> wrote:
> > > Strange
> > > Looking at the header from your email, you came from:
> >
> > mygirlfriday.info
> >
> > > That re
Hi Charles,
On Fri, 24 Oct 2003 22:36:17 -0500 GMT (10/24/2003, 10:36 PM +0500 GMT my
time), Charles Howse wrote:
C> Thanks for that clarification.
You are welcome.
C> I do indeed see you in the logfile at 19:31.
Good, at least WAN wise, you are fine.
C> Now I'm getting spooked! Could I be b
> Hi Charles,
>
> --On Friday, October 24, 2003 08:40:09 PM -0500 Charles Howse
> <[EMAIL PROTECTED]> wrote:
>
> > Strange
> > Looking at the header from your email, you came from:
> mygirlfriday.info
> > That resolves to 65.64.145.209
>
> The above is the address of my remote mail/DNS ser
Hi Charles,
--On Friday, October 24, 2003 08:40:09 PM -0500 Charles Howse
<[EMAIL PROTECTED]> wrote:
Strange
Looking at the header from your email, you came from: mygirlfriday.info
That resolves to 65.64.145.209
The above is the address of my remote mail/DNS server. My static IP that I
conn
> > Try it yourself: http://howse.homeunix.net
>
> I connected without any problem at 20:58 24 Oct (UTC -4:00). I am
> running the same 4.8 version you are.
>
> > Not working as of 19:05 this date, CDT (UTC -6:00).
Check my math here...
You connected at 20:58 + 4:00 = 00:58 UTC
I was down at 19:
> Hi Charles,
>
> --On Friday, October 24, 2003 07:14:21 PM -0500 Charles Howse
> <[EMAIL PROTECTED]> wrote:
>
> > Try it yourself: http://howse.homeunix.net
> > Not working as of 19:05 this date, CDT (UTC -6:00).
> >
> > What in the world could be happening?
>
> I just logged on without a prob
>
> Try it yourself: http://howse.homeunix.net
I connected without any problem at 20:58 24 Oct (UTC -4:00). I am
running the same 4.8 version you are.
> Not working as of 19:05 this date, CDT (UTC -6:00).
>
> What in the world could be happening?
>
> The software setup:
> Apache2
> vsftpd
> Fr
Hi,
For the past week or so I've been pulling my hair out trying to diagnose
what's going on with my website.
Prior to that, everything was working perfectly.
I've made no changes that I was aware of.
There is no pattern to this...sometimes I can connect to the web server
over the Internet, sometim
18 matches
Mail list logo
