I have just installed DNN 5.1.2 on a Windows XP machine with SQL Server 2000 backend.  Everything works in development as it should.  I then attempted to duplicate the installation to its own web site on the production server (under it's own web port) using the same SQL Server (new database, same physical server as the site).  The installation goes smoothly, but once I go to the site, I cannot navigate in any way (including the Home menu, Login, or Register).  I get an error stating " the resource you are looking for...has been removed, had it's named changed, or is temporarily unavailable..."  The requested URL is /Login.aspx, /Home.aspx, or whatever I happened to click.

I can point the XP installation to the database, and everything works normally.

At this point, all settings are default.  The web site I set up to run it is running under port 84; I set UsePortNumber = true in the web.config file;  I am running the site under a domain account as anonymous; the network service account has full rights on the DNN folder.  The Win2003 server is currently running DNN 3.1.2 and DNN 4 on separate sites/application pools, etc. without any problem.

I am open to any and all suggestions.  Thanks!

Is that a question or a statement?  The machinekey values are different between the new site and the existing site (on the same server)?

I stopped the existing DNN sites (v3.x and v4.x), and the new site came up fine.  I was able to briefly run all three sites simultaneously, but the DNN4 site stopped working after a short time.  It appears I can run DNN3 (port 80) simultaneously with either the DNN4 (port 81) or the DNN5 (port 84) site, but not both.  I suspect .Net 2.0+ has something to do with it, because the .Net 1.1 site runs along happily.

I didn't mention before, but each site is in it's own application pool as well as different sites, ports, etc.

I do have a work-around--I have installed the new site onto an "obsolete" server.  Functionally, it's okay, but I need to get it back to a supported server as soon as possible.

Thanks!