Hi,

I have a DNN portal. At my webserver (Win Server 2003 Web edition - IIS6) the default web site is pointed to the dotnetnuke folder, so if people browse to www.mydomain.com, the portal loads automatically as expected. My problem is that this way I cannot use any other virtual directories like www.myportal.com/otherwebapplication, because the other web app is somehow mixed up with dnn. The solution would be the point the default directory to wwwroot, but this way I have to somehow redirect www.mydomain.com to the dnn folder. I'm sure this is a common problem,  is there any best practice for this?

Thx!

Ors     

Thanks for your answer, some more details:

I have the following scenario on my server:

C:\web\public (this should be my wwwroot)

C:\web\public\dotnetnuke (this is the dnn folder)

C:\web\public\otherwebapp (this is the folder of the other webapp)

I have two virtual directories both under default website ponting to the folders above. I don't want other webapp to be a separate website because it's a part of my dnn site (provides a service which is displayed in an Iframe in my portal)

If default website is pointed to dnn folder, my portal loads automatically, but the other webapp doesn't work. If it's pointed to my "public" directory than everything works, but the portal doesn't load automatically for www.mydomain.com.  So my question is how to make dnn load automatically for www.mydomain.com, if default directory points to  the parent directory of dnn and not dnn itself?

Thx a lot!

Ors