installation question: NT and IIS

[Balzer, Ned]

Hi Brent (and others),

Thanks for your help, but I did manage to get myself in trouble somehow.  I
should have mentioned maybe that this server has about 8 IP addresses on it.
First I went into IIS and made sure that all of the websites there were
bound to specific IP addresses, none to "*All Unassigned*".  Then I added a
brand new IP address to the machine, and in DNS I assigned a name to it
(both a forward and a reverse address) -- to be specific, the name is
"manila.cgnet.com" and the address is 198.93.224.82.  And I used the name
manila.cgnet.com as the webserver address during the install of frontier.

But, the frontier webserver will not start.  When I try to start it I get
the error:
Can't bind listen stream because TCP/IP error code 10048 - Address already
in use.

It seems pretty clear what's wrong, that Frontier is trying to bind to a
different IP on the server; I just don't know how to change it.  I looked in
vain for an .ini file or a registry key that might contain this value but no
luck. Nor can I find anything to do this in the Frontier interface.  I tried
to re-run the installation, specifying the IP address rather than the
hostname (went to the Userland site), but just got the error that the server
had already been created.

I thought about changing the port but I'd really rather use the standard
port 80 if possible.

Any help or advice would be appreciated.

-- Ned Balzer
n.balzer at cgnet.com
--__--__--

Message: 1
Date: Fri, 12 Oct 2001 17:14:29 -0700
From: "Balzer, Ned" <N.BALZER at CGNET.COM>
Subject: installation question: NT and IIS
To: "'Frontier-Users at userland.com'" <Frontier-Users at userland.com>
Reply-To: Frontier-Users at userland.com

Hi all,

I am brand new, so I imagine these may be easy questions for many of you and
I thank you in advance for the help.  We just purchased Manila/Frontier and
I want to install it on a Windows NT 4.0 server running IIS.  I have about
10 production websites on this server so I can't afford to break any of them
during the install.  My question is what precautions I need to take.  Should
I add another IP address to the network card for frontier?  Can I get
frontier to answer on a non-standard port (not port 80) during the
installation?  Can manila be made to run on top of IIS rather than frontier?
Is this even a good idea?

I haven't figured out yet whether our preferred use of manila will be to
create statically rendered pages served by IIS, or whether there would be a
parallel set of manila websites to the IIS ones (which use manila features),
but I'm hoping that at least manila can coexist on the same box with IIS.

Thanks again.

-- Ned Balzer
n.balzer at cgnet.com

P.S. if it's more appropriate you can answer privately.


--__--__--

Message: 2
Date: Fri, 12 Oct 2001 18:22:09 -0700 (PDT)
From: Brent Simmons <brent at userland.com>
To: "'Frontier-Users at userland.com'" <Frontier-Users at userland.com>
Subject: Re: installation question: NT and IIS
Reply-To: Frontier-Users at userland.com

Hi Ned -- your best bet is to get another IP address for that machine. Use
IIS on one address and Frontier/Manila on another.

You can also use IIS to serve pictures and other static files, leaving
Frontier free to concentrate on dynamic pages.

-Brent


On Fri, 12 Oct 2001, Balzer, Ned wrote:

> Hi all,
>
> I am brand new, so I imagine these may be easy questions for many of you
and
> I thank you in advance for the help.  We just purchased Manila/Frontier
and
> I want to install it on a Windows NT 4.0 server running IIS.  I have about
> 10 production websites on this server so I can't afford to break any of
them
> during the install.  My question is what precautions I need to take.
Should
> I add another IP address to the network card for frontier?  Can I get
> frontier to answer on a non-standard port (not port 80) during the
> installation?  Can manila be made to run on top of IIS rather than
frontier?
> Is this even a good idea?
>
> I haven't figured out yet whether our preferred use of manila will be to
> create statically rendered pages served by IIS, or whether there would be
a
> parallel set of manila websites to the IIS ones (which use manila
features),
> but I'm hoping that at least manila can coexist on the same box with IIS.
>
> Thanks again.
>
> -- Ned Balzer
> n.balzer at cgnet.com
>
> P.S. if it's more appropriate you can answer privately.
>
>





End of Frontier-Users Digest