ah, your problem is one of portal alias's I think then. When you install dotnetnuke, it detects it's current location via IIS, and add's that as a portal alias. This allows a single installation to respond to multiple different paths, as well as allowing multiple virtualised sites to share the same codebase/database. Before you move a site to production, log into your local copy as the host user, and go to admin->site settings. Scroll to the bottom and add your alias e.g. www.mylivesite.com . Now this DNN instance will respond to both requests identically e.g. localhost/dotnetnuke and www.mylivesite.com will both serve the same content.

Cathal

I GOT IT!!!!

Wooooo Hooooooooo   

Environment:
Windows XP 64 Bit
Visual Web Developer
Sql Server 2000 (remote)

For the initial install on your local machine you dont need to do anything speial.
Just create a new Web Site on your machine, IIS will create the Virtual Directory.
Once the site is created you simply launch it and let it do it's thing..."PATIENCE"
This may take several minutes...wait till you see the link on the bottom of the page to go to
your portal.

Next:
Go into the Database --> PortalAlias table and change the Portal Alial for the first record to your domain.
I was able to get this to work even after copying the files to my host server.

Once you change the information in the database you will need to make the Application re-cahe the
data pulled from the database. The way I did this was to add something smalll to the Web.config file
and re-upload it.

As soon as that was done my site was up and running just fine.


I wanted to thank all the posters here that took the time to help me and answer questions.
And a BIG shout- to the DotNetNuke team...great job!


Does anyone know how to log on as host?

Thanks

Will