I have installed a single DNN instance of DNN v5.0.4 on localhost with WinXP SP2, ASP.net 2.0 and IIS5.1. and have set up a parent portal which registers as 'portalId=1' pointing directly to the root dnn install file directory and a portal alias assignemtn of localhost/website2org (website1com is the primary default portId=0). I've set up two virtual directories in inetmgr and pointed both to the same root DNN install file directory, added the 'default.aspx' to both and checked that I'm on .net 2.0 as well as the permissions access as Integrated. Now when I goto a browser and plug in 'http://localhost/website2org' I am consistently REDIRECTED to the primary default portal.

I've checked around online and read somewhere that IIS5.1 may not allow multiple parent portal sites but I thought the DNN installation took care of that via Portal Alias assignment (a.k.a. host headers). As a possible fix I've tried the following:

1) Added in the HOST HEADER file '127.0.0.1 website2org' but this did not work;
2) In Host settings>SQL tried the SQL query  'UPDATE PortalAlias Set HTTPalias='localhost/website2org' Where HTTPAlias='website2org' or HTTPAlias='website2org' -- this did not work and now my DNN installation seems to have taken a performance hit as a result;

Both two options above left me with the same redirect problem and now I've read a third option of make the parent portal a child portal but I REALLY REALLY would like to figure out some way to get multiple parent portals working on a single DNN install to work on localhost.

Can anyone be so kind as to direct me to a newbie's rudimentary networking/code knowledged individuals step-by-simple-step guide to makeint this work???

T h a n k s!!