domain/IP + server problem (problem reproduced;even more info)

[Paul Welty]

Well, the saga continues. But this time, I think I see what the problem is,
and I can't see how it's anything's fault except Frontier.

Here's the latest story.

At some point last night, my dynamic IP changed. The dynamic domain name got
updated, like it was supposed to, and everything resolves correctly. But
Frontier doesn't listen any more. No matter what I try to do, Frontier now
won't respond to anything on port 80. The Filemaker server at port 81
updated just fine and responds now to the new domain name/IP address, but
Frontier won't.

I'm positive the domain name resolves correctly, and I even tried getting to
the server using the (new) IP address from another machine, but it just
hangs. No errors, no nothing. If I switch to port 81, then the FileMaker
server responds with no trouble.

So, why won't Frontier listen?

I quit Frontier and re-ran it. Same problems.
I quit Frontier and restarted the server. Ran Frontier (re-forwarded the
port 80). Same problems.

The control panel will open at localhost:8080, but it very oddly reports on
the "home" page that it "Can't coerce the string "" into a floating point
number" and does not display the usual host info (like IP address). What
gives?

The control panel does _not_ report the correct Manila sites that I have
created. What's going on here?

The daily log, under mainReponder, does not report any hits when trying to
get to the Frontier server except using 127.0.0.1:8080.

Using 127.0.0.1:80 generates a 401 error, but at least that seems to come
from the server, and indeed the log logs it.

So, why isn't the IP address getting though to Frontier when it was before
the dynamic IP changed? What about a changing dynamic IP frustrates Frontier
or OS X?

The last x times this happened I had to completely re-install Frontier to
get it to work. Is this the solution to having a dynamic IP with Frontier?
Surely not.

What am I missing?

Getting perplexed and frustrated,

Paul



On 4/7/02 12:17 PM, "Ken Dow" <Me at KenDow.Com> wrote:

> Paul,
> 
> Another thought about your domain versus IP experience - did you read
> the Installing Frontier.html file in the Frontier folder and follow the
> link to the Proxy Read Me.html? This could be one source of your
> problems. HTH.
> 
>> Well, it's working again. And, of course, I have no idea why.
> 
> --
> Regards / Ken
> http://www.kendow.com
> 
> I arise in the morning torn between a desire to improve the world and
> a desire to enjoy the world. This makes it hard to plan the day.
> - EB White
> 
>