Hi, I followed (at least I think I did) your detailed post, but I was unsuccessful.

I needed to move our dotnetnuke website from one server to another. Basically we got a new server and scrapping the old one.

The scenario is as follows:
Hosting the website in-house
Old server was called 'DNN'
New server is called 'DOTNETNUKE' (very original )
Steps carried out:
1. Copied the dotnetnuke installation from DNN to DOTNETNUKE.
2. Took database on DNN 'offline' and copied to DOTNETNUKE; then I put back database on DNN 'online'. (variation from backup/restore)
3. Created Virtual Directory and made the necessary settings, including ASP.NET v2
4. Edited web.config ConnectionStrings and AppSettings from DNN to DOTNETNUKE. (I am still using the same SQL username and password)

Loading dotnetnuke from the new DOTNETNUKE server as http://localhost/dotnetnuke will not load at all. The blue 'loading' bar starts moving but never finishes and the w3wp.exe keeps hogging 25-35% of CPU infinately.

Loading from the old server as http://localhost/dotnetnuke will load instantly.

At this point I think the portal alias should not affect since I am still trying to load as 'localhost'.  I was hoping that after it loads, I would change the portal alias then.  Anyway the portal alias for the outside world would not be changing either.

What did I miss out?

Thanks
Chris

Thanks for your post; however I left the virtual directory as 'dotnetnuke' on both machines, so they should both be 'http://localhost/dotnetnuke'.

The only thing that changed should have been the host machine's name from DNN to DOTNETNUKE.

Anything else I can check?  What about the machine keys in web.config?  Should I need to change these because I left the web.config file 'as is' from the old machine, except for the SQL connection strings.

Thanks