Hi atmchuck,
Not sure if I understand what you are saying.
I created the first (original) the exact way they said to install it.
I then created a second parent portal from with in the Host menu. alias "servername/portal2"
But that didn't seem to work...kept getting a 404, like DNN couldn't find the site.
So, using the replies from this post, I created a "portal2" VD within IIS and pointed it to the "website" directory of the DNN install. Then it seem to work fine.
If this is NOT the way that I am supposed configure a second portal, please let me know...I am about to install DNN on my production server and would like to configure it the correctly right from the start.
Also, I just thought about this...On my production box, when I create the portals, should I use the actual external URL as the alias?
Meaning, currently on my dev server I have the portal aliases set to "servername/portal1" and "servername/portal2".
But of course I would like, on production box, the portals to use the real URL: http://www.portal1.com and http://www.portal2.com when users go to it. Should I set the portal alias, on the production box, to the real URLs instead of servernam/portal1 and servername/portal2?
Or do I set it up just like I did in dev and use "host headers" for the URL definitioins?
Thanks very much in advance!!