if you are running in a virtual directory, you cannot create a second parent portal with a different vdir name, i.e. localhost/dnn2, only subportals like http://localhost/dotnetnuke/portal2. If you are using domain addresses, like http://dotnetnuke1 and http://dotnetnuke2, they may easily get bound both to the same IIS web site and DNN will route it properly to the different DNN portals, if portal aliases have been added appropriately. To make this working you need to add both domain names into you local windows\ system32\drivers\etc\hosts file using a text editor.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

I hate to keep bumping this post, but I would love to get started on DNN. Does anyone else have any ideas? I can't tell if it's my configuration or if I just don't understand how DNN is supposed to work.

I think I finally found my answer in this post: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/286824/scope/posts/Default.aspx I was missing the importance of Parent Portals having a different domain, which sounds possible to do with host headers in IIS 7, but not in the version I have (IIS 5.1). I guess I'll just experiment with the default portal (http://localhost/dotnetnuke) for now.