I've done this before, so I'm not sure what the problem is; but I just setup another parent portal on my server and when I browse to it, I'm getting redirected to the default portal. I've double and triple checked the alias and it's correct. IIS seems to be setup correctly and I don't see any conflicting IIS installs. I'm truly baffled at this point. If anyone has any ideas, I'd love to hear them!

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

I am having the same problem, and I'm kind of a newb in DNN, so I probably don't understand the difference between child/parent portals (is there a document somewhere I can read??)

I have my "main" portal which was setup when I installed DNN (4.03), and I now added a new portal via host->portals->add new portal.  I had setup my IIS to point to my DNN directory.  So my setup looks like this:

IIS:

localhost/portal1 points to my DNN directory (which is in inetput/wwwroot/dnn4)

localhost/portal2 also points to my DNN directory (which is in inetput/wwwroot/dnn4)

and I have two portals setup by the name of portal1 and portal2, each configured to find the alliance localhost/portalN where N is the number of the portal, with portal1 beind the "main" portal I started with.

For some reason which is beyond me when I access localhost/portal2, it always redirects to portal1!!

Please, can someone wiser than myself explain what it is that I'm doing wrong??

Thanks!!