Multihomed Server Configuration comes full circle.

[John Sitka]

Hi,

Windows 2003 Server
WSS
Project Server 2003

When I first installed WSS and followed the Road Map to installing Project
Server I ran into a
very diverse bunch of issues that show themselves in confusing ways.


http://groups.google.ca/groups?hl=e...3Rn1NrQEHA.2400%40tk2msftngp13.phx.gbl&rnum=2

and



http://groups.google.ca/groups?hl=e...uLsojA2QEHA.624%40TK2MSFTNGP11.phx.gbl&rnum=1

I resolved these issues by.

Saving off the various root directories of IIS and noting the configuration
of virtual ones
Removing the server role Application Server.
Removing all but the single IP address you want WSS/Project Server to work
on from the NIC.
Reinstalling the Application Server role.
Following the WSS/Project Server Road Map.
Adding back the various IP's that you would want to use for other websites
Adding a new site(s) and typing in the new IP's for it because it probably
isn't in the IIS metabase and
therefore not in the drop down list of the website properties console.
Edit DNS records to fit.

So if you need to get WSS or Project Server placed on some dual duty
webservers I think this may help
but don't use it as a guide. It is more of an insight to understand the
assumptions Project Server makes
on behalf of itself during setup and subsequent behavior.

Thanks to those that helped.