Hi

I had the exakt same problem. Can you not solve it by adding a Portal Alias in your "Site Settings" (on the bottom)?

I had the problem of haveing installed and set up the entire site through localhost. When I tried to access it through the computers IP address, it redirected to localhost. I solved this problem by adding a new Portal Alias in the "Site settings"

OK, I found the problem, so here's what I found for all those who come later and find this problem.

In our current hosting environment, we are using a shared server - meaning that I have no administrative control of this machine.  After uploading the database and DNN files, I had made a change to my local database and pushed the changes up to the live server (using Red Gate's SQL Compare, a fine tool by the way).  One of the changes that was pushed up to the server was the PortalAlias value, which on my local machine was still set to the name of that machine rather than the live domain name.  Now I didn't find any problems immediately because the ASP.NET application continued running.  When it shut down sometime that night, the PortalAlias value was re-read, and subsequently caused the error.

The fix that finally worked was to update the web.config file on the server.  NO actual change was required; however, when you modify and save the web.config it forces the ASP.NET application engine for your site to be restarted.  I just added a line break, removed it, then saved the file, and the updated modification date on that file caused the app to restart and the site began working normally.