Does anyone have a link to some useful informaiton on properly setting up multiple top-level sites on a WSS 3.0 farm? I've been searching around MSDN, but haven't seen what I'm looking for yet. We are on an intranet environment and have a successful SP farm (2 servers) running with a single top-lavel site running on port 80 (several sub-sites). We have now been asked to setup multiple top-level sites (not living under the current site) for different branch locations, each will use their own FQDN (still intranet, so internal DNS). I'm looking for the best practice on setting up this scenario for 1) setting up the sites in SP, but also 2) getting the correct IP/port scheme working in conjunction with DNS so that each site just has a FQDN they use, not specifying a port in the URLs (maybe DNS can handle various port redirections for us?) Ideas? Thanks in advance...

From what I am understanding, I think you have at least two options: 1. You can look into using SharePoint's host-named site collections to give you this functionality. You will want to start with this article and be sure to test it because there are some limitations with this type of site collection: http://technet.microsoft.com/en-us/library/cc288637.aspx 2. You can use IIS to do redirects from the host header you setup to a subsite on the SharePoint server. This will change the url the user sees in the browser but let's them type in the FQDN this wish to in order to get to the site.JD Wade, MCITP SharePoint Consultant, Horizons Consulting, Inc. Blog: http://wadingthrough.com Twitter: http://twitter.com/jdwade