Hi DNN Pros,

I'm restoring a backed up site and DB from one Windows 2003 Server machine to another on the same intranet where host headers are used.

I followed "standard" (if such a thing exists) backup/restore procedures.

When I run my restored site for the first time, I get redirected to the original location. I tried the same procedure on the same machine (basically duplicating my site and DB) with similar results.

How can I fix this?

Thanks

Rad

Jeff Cochran wrote Sounds like either your DNS still points to the old system or you need a new portal alias to match the new system. Jeff

Thanks Jeff.

I'm on an intranet where no DNSs are involved. At best, I'll add an entry to the hosts file on my local machine so that I won't have to type the full <localhost/...> path in the address bar.

So I guess it comes down to the Portal Alias. It seems to me it's a bit of a Catch-22:

I want to backup/restore my site on a local machine because I don't have authority to make changes in a Production environment, BUT I can't access my local installation unless I add a new Portal Alias in the Production environment. Is this what you're saying?

Again, my problem is that as soon as I access http://LOCALHOSTt/site (which was correctly restored, BD too), I get redirected to http://PRODUCTION/site (using Production DB). 

Does this not simply boil down to some database and/or .config file setting(s) on my local machine? Can these settings be changed manually, without using the DNN interface? What .config settings do I need to change? What DB table rows need changing?

Thanks again

For some strange reason the second portal alias was not appearing in the site that resulted from the DB restore. It is possibile that I only added the second alias after doing the DB backup and not after. Sorry for any confusion.