Chris,

Well, I gave the revisions a try this weekend and didn't have any luck.

1. I added the "mymainsite.com" as a new alias to the current DNN installation.
2. The skin files are ascx and using an editor I didn't see any reference to the /site/ folder in any path. Just "<%= SkinPath %>" embedded in the code. In fact, I looked through quite a few of the file residing in the DNN folder and couldn't find any direct references that included the "/site/" folder in any path(s).
3. I changed the original "/htdocs/" within the DNS cpanel to point directly to the DNN installation in "/htdocs/site/" at the hosting provider.
4. At that point the website shows up but with no formatting and by looking at the page source code using the browser "view source" option I can see where the "/site/" folder is still embedded in the paths of all file / images / etc references.
5. And, of course, I couldn't login to do anything with DNN because now clicking the login link would be misdirected and result in a page not found...

I reset the site path at the DNS back to "/htdocs/" and the primary site is back up and running normally.

Any ideas on how to proceed? Thanks again for all of your help!

Jim

I thought of that (it's one of the steps in your instructions) but I couldn't login. When I click the login I get a page not found error. But, to tell you the truth, there are quite a few pages on the site that would have to be manually tweaked to remove "/site/" from the paths (images / links / etc) that I would be worried that I missed too many.

I spoke to my client and they are okay with just arranging for another hosting account for the new site. This multi-portal thing sounds great, but it also sounds like it's problematic if DNN isn't setup and running out of the hosting space root folder.

Thanks again for all of your help.

Jim