I tried reading the FAQ above, and it seems like maybe something to do with this is my problem:

Q. What if i am restoring a site on a different server, the URL of the restored site is different, and i did not add the new http alias in the old site?
A You can manualy add a new portal alias by entering  new record in the table PortalAlias. Enter the proper PortalID (0 for your first portal), and a proper alias (whithout "http://" ). You need to do this before you browse to the new site for the first time. DNN caches the entries in the PortalAlias table, so if the record is added after the first request to the site it will not be seen. Should this happen (ie, you are redirected back to the URL of the old site), just recycle the app pool, or reset IIS to clear the cache completely.

'but I'm not really sure what that means.

Could someone point me in the right direction, please?

My dev environment is Vista with VWD Express, and the site runs fine when I push build or access it using IIS.

I copied the entire subdirectory to my Windows 2k3 webserver.

The folder has full permissions for both aspnet and network service users.

When I attempt to access the site, I just get a "cannot be displayed" error.

I noticed, when I type in the IP like "http://xxx.xxx.xxx.xxx" the browser reverts to "localhost\[Name of DNN SubDirectory on Dev computer]"

Is the FAQ above relevant to my problem?

Do I need to somehow open the Database.mdf file from the App_Data directory?

Thank you!

(As an aside, I have another side defined on this server, and I was able to setup a DNN install from scratch there... just wanted to make sure that it worked)