Ok.  Here's what I've got.  XP Prof SR2.  I've got DNN 4.3 working and I've got IIS pointed to my DNN site.  I've got it setup with two portals.  The first is www.eol3.com.  The second is denny.eol3.com.  When I http in to either, I get the desired portal.

Now, I also want to be able to create my own ASP2.0 pages and get them to work.  I've got VS 2005 Web Developer Edtiion and I've created a simple page that works just fine in VS.

I created a folder on my C-Drive. I've webshared it at /Test. 

When I do www.eol3.com/test/index.htm the simple HTML document loads just fine.

I've put the web.config from my ASP2 project along with the Default.aspx and Default.aspx.vb in the /test folder.

The silly application WON'T WORK.

ASP 2.xxxx is setup for the folder.

For some reason that I have yet to understand (I'm new to all this -- I'm an IBM iSeries programmer primarily) the web.config from the website is being read and it causes errors with my ASP2.0 application yet it works just fine for DNN.

Is this something resolvable without messing up DNN?

Is this something where having MS Server 2003 R2 would be the better option?

Regards,

-- Elmer

No, you've got it right.  I want my website to come in to the DotNetNuke as I like the multiple portal feature.

I originally started out with just a page at www.eol3.com and set it up so that from there people chose their DNN site.

But, the more I got into this, the more I decided I wanted to be able to have DNN pick the portal from the incoming domain.

Now, when they go to www.eol3.com, the host web is displayed but if you go to denny.eol3.com, you get his portal.  I like this as with a portal alias, when he gets his domain name, all I have to do is point it at www.eol3.com and add his new domain to his portals alias and whala!   www.myfriend.org goes right where he and I want it.

But, I thought I could create a www.eol3.com/test and do some ASP2 stuff there but I get a bunch of web.config errors.  I put a copy of the web.config that works in VS 2005 Web edition with the internal webserver but it won't work on the IIS server the way I'm setup.

I've been looking at the microsoft servers and the MS 2003 Web edition might be my ticket but $399 is a bit more than I want to put out for this.

Strange though it may seem, I'm not out to make money here.  I just want to be able to help some of my friends put their ministerial works on the 'Net.

I can with DNN.  I just can't put up non-DNN ASP2 sites.  Straight HTML works just fine.  www.eol3.com/test/index.htm loads just fine.  I have not tried a .ASP.

-- Elmer

Check out my blog post about running a webservice within DNN, it may help you on getting another app running in a virtual directory.

http://dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1085/Default.aspx