domain/IP + server problem (moreinfo)

[Paul Welty]

Well, now I've done it. I restarted the computer and the server.

Now, nothing works again. Could it be that Frontier is no longer waiting on
port 80? (Although...I can't see anything on port 8080 either, so I have no
idea what the problem is). As I recall, Ken mentioned that that needs to be
set at each startup.

But, I have no idea how to make that work. Can anyone tell me how to get
Frontier to listen on port 80 (instead of 8080)?

TIA,

Paul


On 4/1/02 3:05 PM, "Paul Welty" <1pwelty at bellsouth.net> wrote:

> I did this, and I found something odd. The IP address returned did not match
> the IP address in the config.domains table. Once I changed this, the Manila
> sites started working.
> 
> I don't know why the domains table was out of whack. Maybe that's the final
> piece of the online setup that wasn't getting complete when the process hung
> up. I'm not sure.
> 
> Anyway, it looks like it's working (for now). Thanks again for helping get
> this straight.
> 
> Paul
> 
> 
> On 4/1/02 10:00 AM, "Ken Dow" <Me at KenDow.Com> wrote:
> 
>> Paul,
>> 
>> Something doesn't sound right here. What do you get when you run the
>> following in the Quick Script window (type Command - ; to display it and
>> then click the arrow button to run the script):
>> 
>> tcp.myDottedID()
>> 
>> Also - did you say that OS X Web sharing was turned off on this machine?
>> 
>>> I gave it the computer admin password (not the Manila password), and it
>>> didn't complain. So, I guess it worked.
>>> 
>>> I used the default 80 - 8080 ports in the setup.
>>> 
>>> Two days ago, using just the IP address, this seemed to work fine.
>>> But, I
>>> haven't installed or de-installed anything since then. So, I have no
>>> idea
>>> what's happening.
>>> 
>> 
>> Regards,
>> Ken
>> 
>> 
> 
>