I am having a very weird problem with DotNetNuke 3.2.1.  I installed DotNetNuke on a test server running Windows 2003/IIS 6.0.  I created it as a Virtual Directory under the default website and everything worked great.  Now I want to deploy it to another server running Windows 2003/IIS 6.0.  I backed up the database, and the directory structure and created a new website on this server and everything looks great.  However, when I attempt to login nothing happends.  I check the logs and it says that I have logged in successfully, but I am not presented with the "admin dropdown", "host dropdown" or the module that appears at the top of the screen.  The only way I can get it to display the appropriate interface is to create a virtual directory under the default website, and then everything is presented correctly.  Can DotNetNuke 3.2.1 be installed as a full blown website rather than a Virtual Directory?  The install guides only make reference to a virtual directory.  I can't for the life of me figure out with DNN would care if it was a website, or virtual directory.  Any assistance would greatly be appreciated. 

I do have one last question.  Can you install 2 instances of DNN on a server?  I would like to have a "production" copy of the DNN install, and then a "test" copy to mess around with and for training purposes.  Thanks in advance for your assistance!

You would be 100% correct I think.  I have included the steps that we followed below in case anyone else has this problem.  Some of them might be unnecessary, but this is what we did to get it to work. 

1) Deleted everything from out previous attempts on that server.

2) Created a new directory for our files, and triple checked to make sure the Network Service account (windows 2003) had full control, and copied our contents/modificiations into that folder.

3) Created a new website with a new IP. 

4) Verfied that the PortalAlias table referenced the IP address only (no DNS yet.  This was causing us problems with the ISA server on the network we believe, or an incorrect DNS entry.)

5) Tested, and everything looked good!

6) Created an A record in DNS for internal use, modificed the PortalAlias table yet again, and tested.  Everything looked good!

If you are going to create 2 like I mention in the post, we stopped the working version of the DNN installation through IIS, just to be sure, and then repeated the steps.  Again... I am sure there are a lot of unnecessary steps up there, but that is how we got it to work.  Thanks Crispy for your assitance!