We have an old version of DNN running as our production website (version 04.09.00).  My manager is fearful of upgrading to a newer version because of the customization done to the code before I started with the company.  In any event, we need to spawn another copy of the same side on a dev server (staging.website.com) and I seem to be running into issues. 

As far as I can tell, IIS is set up correctly.  I made a copy of the production database and production file system and moved it over the the dev server.  I changed the portal alias in the DB to match the staging URL and changed the host setting similarily.  I edited the connection string to reflect the new server and db name.  I even searched the file folders for any reference to www.website.com and replaced them with staging.website.com.

Then I went to the staging site.  It looked great!  It looked just like production...until I clicked on a link.  It looks like the home page is the only one that will work, every other page I've tried (and I've tried a bunch) come up with the same "The page cannot be found" error.  I know it's hitting the database because all the dynamic data and configurations from production is showing up.  Any ideas why this is happening?

I will admit, I don't know that much about the portalalias concept but from what I can tell, it's ok.
PortalAliasID: 4
PortalID: 3
HTTPAlias: staging.website.com

There is an entry in the Portals table for PortalID 3...all from the production site and works there.

 I don't understand the question.