Background: Windows Server 2003, DNN 4.05.05

If I type in www.mydomain.com it shows me the default web site, not the DNN portal.

If I type in www.mydomain.com/dotnetnuke, it redirects me to localhost/dotnetnuke which is the main original portal of DNN, not the new portal I setup.  The new portal I setup has www.mydomain.com as an alias.

Why does it redirect to localhost/dotnetnuke when I attempt to open www.mydomain.com/dotnetnuke?  Hence I can't access my new portal at all.

I got the site up and running.

As to your question regarding not having to enter "/dotnetnuke" to the URL, I found two solutions, neither of which I like.  One is that you put the DotNetNuke files right into the root directory of IIS.  The other is to create an ASP page that does an If Then or Select Case to redirect the user to the "/dotnetnuke" if it's a certain domain.  If it's not, then it will show the default doc in the root.

I have a Win 2003 Server so I can have multiple websites.  I'm trying to setup a website (not virtual directory) and load the DNN files in the root of that website, but I haven't gotten that to work yet.  This would eliminate the redirect or having to load the DNN files in the root of the default website.  If you're running on XP, you only get the one default website, so you'll have to work the redirects or install the DNN files in the root.

Anyone have any comments on my statements?  Is this correct?

FYI for anyone who still didn't get this.  I had the same problem, fresh install, everything went to localhost/dotnetnuke.  It seems the Portal Alias setting is picky.  For example, I put in www.mydomain.com/dotnetnuke/ and that wouldn't work at all.  But as soon as I put it mydomain.com/dotnetnuke (no extra slash, no www) it worked perfectly.