domain/IP + server problem (moreinfo)

[Paul Welty]

Well, it's working again. And, of course, I have no idea why.

According to suggestions from Ken and Sam, I read about port forwarding and
looked into it via the Terminal. I made several changes and nothing worked.

As a test, I quit Frontier and reset the ipfw table. I started Apache and it
worked fine.

So, I quit Apache, trashed the current Frontier, restarted, and installed a
fresh copy. I setup using a domain name (not the IP address) but it didn't
work.

I repeated this procedure, but used the IP address. This time, for whatever
reason, it worked.

To further test, I reinstalled _again_ but went back to using the domain
name in the online installation process. This time...it's working again.

To make it official, I _restarted_ then ran Frontier and used it to re-set
the port forwarding. Still working.

I checked the ipfw table throughout the process and it is _exactly_ the same
now as before...when this wasn't working. So, I suppose the ipforwarding was
never a problem.

At this point, I can see only 2 possibilities for the problem. 1) Frontier.
Even though the requests were being IP-forwarded correctly, perhaps Frontier
was refusing to listen (for some reason). Or 2) ipforwarding. Perhaps
something wasn't working correctly despite appearances. It's certain at
least that I'm not sufficiently informed to completely troubleshoot this
area.

At any rate, thanks again to everyone. I wish I could provide more
information about how this got fixed, but I really can't figure it out.

Paul


On 4/6/02 1:53 PM, "Ken Dow" <Me at KenDow.Com> wrote:

> Paul,
> 
>> This server is behind a firewall, and the firewall routes port 80 to
>> this
>> machine's local IP. (As well as port 81 --- for FileMaker).
>> tcp.myDottedID reports the _local_ IP. Does this mean that Frontier will
>> ignore requests on port 80 that aren't "for" the local IP? even when the
>> port 80 requests get sent to it?
> 
> I'm not sure I understand your setup or what you mean by a local IP, but
> you can specify the IP address that  Frontier as a third parameter when
> port forwarding, like this;
> 
> userland.portforward(80,8080,"192.168.10.9")
> 
> There's more information on OS X  and Frontier here:
> 
> http://frontier-
> osx.userland.com/directory/446/questionsRelatingToRunningFrontierAsAServer/
> howDoIGetApacheAndFrontierServingOnTheSameMachine
> 
> And especially in the Setting Up Frontier section of this:
> 
> http://frontier-
> osx.userland.com/discuss/msgReader$445?mode=topic&y=2001&m=5&d=13
> 
> HTH!
> 
> --
> 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
> 
>