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

[Paul Welty]

Well, there is definitely something very weird going on.

Specifically, I can _not_ re-install Frontier using port 80.

When the online setup is complete, Frontier opens a new browser window to
take me to the control panel. Every time, the connection hangs at this point
because Frontier never answers

BUT...if I change the install port to 82, then everything works fine and
completely as expected.

Apache is not running, so it can't be that Apache is using port 80. (But,
here is something even weirder. In troubleshooting all this at the
beginning, I found out that Apache was on! Of course, I turned it off again.
I had checked this only as a formality, and I'm certain I never turned it
on. What's up with that?)

So, is there some conflict over port 80 that isn't obvious to me?

Paul


On 4/14/02 3:47 AM, "David A. Bayly" <dbayly at udena.ch> wrote:

> Paul,
> 
> I've been sending crash reports since Frontier 7.0.1 that seem to be
> triggered by a renewal of the lease of a dynamic IP from a  cable
> modem company. When dynamic IPs are assigned, they are typically
> assigned for a limited duration.  When the lease runs out it is
> automatically renewed (and the IP migth chnage at this point) , and
> in the process on a Macintosh,  TCP services are momentarily
> suspended while the OS redoes its bookkeeping. At this point my Mac
> often crashes, I surmise because it doesn't handle the notification
> correctly and carries on regardless. I need to reboot to recover,
> whatever Frontier does is irrecoverable.
> 
> This isn't the same problem as you describe, but it points to some
> crashy bugs in the same general area.  There's also  a number of
> things that appear to go wrong if you run with 2 IP addresses for the
> same server.  Again it mostly works, but there are some odds
> situations that just aren't handled correctly.
> 
> Not much help, but a type of confirmation.
> 
>