Heya everybody,

I'm pretty new to this DotNetNuke thing, coming over from using Joomla on most of my websites. I recently got DotNetNuke installed using Windows Server 2003 and IIS with Microsoft SQL 2005 Express. The install went well and I've got a working copy of DotNetNuke installed, but there's a slight snag (and forgive me if this has been covered, I did a search but couldn't find what I was looking for).

When I go to my site on the server, even if I put in my .com it takes me to the proper directory and DotNetNuke shows up, but I noticed that my URL bar goes from http://www.mysite.com/DotNetNuke to localhost/DotNetNuke. I didn't think much of it until I tried to get to the instance of DotNetNuke from outside the server, where the same thing happens; only obviously it isn't going to find DotNetNuke on the localhost of a client that is trying to connect to the server.

I figure this has to be some simple line in a configuration file but I'm so unfimilar with the software that I can't find it. Any ideas anybody?

Thanks for the help!

John Herreshoff

I'm new too and i have been working with DotNetNuke for about 3 hours now.  I had this exact same problem.

here is the solution I found:

• on your web server, login to DotNetNuke as 'host'.
• choose menu item Host | Portals
• click the edit icon beside the portal you are unable to reach
• scroll down to Portal Aliases and click Add New HTTP Alias
• In the 'HTTP Alias:' field, enter <your external dns>/<virtual directory> (ex. <your external dns> = mysite.com and <virtual directory> = DotNetNuke)
• Click Add New Alias

I'm surprised there isn't a step during the setup process to prompt the user to add an alias for the current host name.

Yup, I figured it out about 30 seconds before you posted your reply. Thanks for the help!

This DotNetNuke thing is still completely new for me. I'm used to working within Linux, Joomla and PHP and this whole Windows Server 2003, DotNetNuke and ASP thing are completely foreign to me. It looks like it'll probably fit my needs better, though, as I'm going to have pretty average people editing the content that's in the portal so the closer to looks to Windows and Microsoft Word, the better.