domain/IP + server problem (moreinfo)

[Paul Welty]

Aha. This points to what must be the problem. And it brings up something
which I incorrectly failed to mention. So, if it turns out this omission is
the problem, I will be properly embarrassed.

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 never thought this could be a problem because FileMaker didn't seem to
think this was a problem and because Frontier did actually work with this
setup before the restart. So, there must be some setting somewhere that
somehow got un-set and would fix this on Frontier.

Feeling optimistic, if a little embarrassed...

Paul


On 4/6/02 10:58 AM, "Ken Dow" <Me at KenDow.Com> wrote:

> Paul,
> 
> How about running this command in the QuickScript window again:
> 
> tcp.myDottedID()
> 
> Last time it turned out the IP address wasn't what you expected. Could
> it be there's more than one IP address configured on this box? And that
> FileMaker is binding to one IP but Frontier to another?
> 
> On Saturday, April 6, 2002, at 10:46 AM, Paul Welty wrote:
> 
>> Control Panel works (on 127.0.0.1:8080) but still nothing else does. I
>> can
>> create a Manila site, but I can't get to it.
> 
> When you say "can't get to it", what error exactly are you seeing? And
> are you using the localhost (127.0.0.1), the IP address you expect
> Frontier to respond with, or the domain name?
> 
>> But, going to 127.0.0.1 gives me the correct response based on the
>> "default"
>> setting in config.mainResponder.domains. So, it looks like the
>> webserver is
>> working and the port forwarding is working.
> 
> Assuming your seeing a browser/DNS  error and not a  Frontier error,
> this suggests suggest to me that Frontier is fine and we're missing
> something about your DNS or TCP/IP config.
> 
>> It seems crucial to me that 127.0.0.1 works but that the IP address
>> doesn't.
>> But, I have no idea what that might mean.
> 
> Me too.
> 
> --
> 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
> 
>