Hi,

I have a default DNN installation. I now need to create multiple parent sites on my local machine for testing purposes. I followed the excellent tutorial on "Creating Parent and Child Portals" which I understand for a live server.

How do you configure DNN and IIS to use localhost for multiple parent sites?

I have tried to create a new virtual directory that points its local path to the DNN installation folder on the hard drive, I then set up the new parent with alias "localhost/testsite".

When I try to navigate to "localhost/testsite", I get "localhost/dotnetnuke" which is my default install.

Where am I going wrong?

Thank you in advance for your time.

Dave

For localhost testing, I would set everything up as child sites.  That way, everything is localhost/dotnetnuke/sitex, etc.

When you move this to a remote hosting location, you really don't have to do anything except (1) add portal aliases for the actual domains to the table and (2) have your host (or whoever manages DNS) point your domains at your single DotNetNuke installation.

Here is an example.  I have a site that has a single parent and multiple child portals.  Several of them are (portal aliases in parens):

jncraig.com
jncraig.com/sbhs65  (sbhs65.org)
jncraig.com/patapsco (patapscorg.com)

Now, I can use the child domain to visit the site, but I can also use the domain name.  I have sbhs65.org and patapscorg.com pointed at my DotNetNuke installation.  When requests come in for any installation, DNS forwards them to IIS with my address,  IIS forwards them to my DotNetNuke installation, and DotNEtNuke figures out which portal the resqest is for.

Setting everything as a child portal works great! I think that I will be using this method for development.

I would still like to know if it is possible to setup multiple localhost parent sites though.

Regards and seasons greetings!

Dave

Yes, you can set up multiple parent sites.  It's just a tad more involved in setting up the correct pointers, etc.  This is especially true if you want to access the sites from other computers.

I don't have some existing instructions to send.  And, since it's fast closing in on Christmas ... remind me if you'd like some more instructions.

For multiple parent portals in localhost, setup IIS in exactly the same way as you do for the original DNN installation.

So, create another virtual directory in IIS, point it to the same DNN installation folder and from there you have the url you can use for your parent portal.

Hope this helps, thanks,

Thank you very much, that worked!

I honestly thought that I did that before but I guess I must have missed something.

Thanks again both of you.

Seasons greetings!

Dave

That worked for me, also. Glad I found this post.

Thanks!

Ken

I am very new to DNN and IIS.

My parent portals do not work for me. I followed the instruction. I am still have no idea how to get it working. I am using window vista ultimate. Would that the configuration in IIS will be different from XP?

In IIS, under the Default Web site. I created the virtual directory. And, the physical pointing is to the original dotnetnuke "install" folder(dotnetnuke folder located in the wwwroot file). Are my steps right?

In the GUI create new portal interface, what I should put in for the alias text box?

These steps are not working for me. I am very confused with the configuration. Can someone tell me how to do it?

Thank You.