Hello all,

Please disregard this post. I've solved the "mistery " already. Sorry, I didn't inform you guys earlier because I was so busy with my projects. I got the trick already. I realized that the production site I'm using is using a different port number and different Host Header Name that was why every time I point the URL to localhost (port 80) it's gives me the "freaky" "Page cannot be found." error because the port number it is using is port 7777  . I almost lost my mind! Grrrrrrrrrrr!

To those encountering the same scenario, please follow this steps:

1. Before you move your database from one server to another, make sure you already created a Portal Alias for the portal you are going to use for your site, else you will need to modify the Portal Alias table on your database. (Remember to check the port and the Host Header name your production server is using, else you'll be trapped). This is very important if you will run your site on the intranet.

2. Detach the database, zip it, attach it to your production database server.

3. Zip the entire DotNeNuke folder and unzip to your desired location on your production server.

4. Open IIS and create a new website, then point the root directory to your new DotNetNuke folder. Configure all the site settings, permissions...bla bla

4. Modify the web.config file, change your database settings to point it to the new database server. If you are using DNN 4.x, you will need to modify 2 databse settings:

One for the Express Edition and the other for the backward compatible version.

That's it.

5. And everything should work. Mine is working now.

Good luck!

Happy Nuking!

eleanor