domain/IP + server problem (possible solution)

[Paul Welty]

I've been trying and retrying all the ideas from this list and from the
various Userland websites (some of which are very hard to find, much less
browse). Nothing was working.

So, I decided to start with a different premise. Perhaps all these failures
to troubleshoot Frontier meant that Frontier is not the problem.

So, I looked at OS X, including all the ipfw stuff. Nothing was working
there either. So, next step...maybe OS X isn't the problem.

What's left? Well, in my configuration, I have a router whose function it is
to pass on port 80 traffic as well as 81 and some other ports to the
development server. Just as a test, I reset the router. And voila,
functionality returned on port 80.

My current operating theory is that somehow the router went foo and stopped
passing on port 80 _only_. The other ports never stopped working. This may
be caused by some glitch in the router when the dynamic IP address changes.

I have an email in to the router people to see if this could be the problem.

In the meantime, things are working again, and this time I have an idea of
why. I'll be sure to test this theory if/when the setup stops working again.

Thanks again to everyone for their help.

Paul


On 4/14/02 9:18 AM, "Paul Welty" <1pwelty at bellsouth.net> wrote:

> 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.
>> 
>> 
> 
>