Are you trying to reach it from the same machine it's running on and is one of the entries you have in PortalAlias localhost/DotNetNuke?

---

Paul Davis

Your post (possibly) doesn't really help the guy. At least, I can say I don't fully understand why you asked this question... but here are my thoughts:

It really depends on how you set it up in IIS. If you installed dotnetnuke to your Default Web Site's root directory (often this is "C:\inetpub\wwwroot") then you would need/want to add "localhost" as an Alias, and not "localhost/DotNetNuke". Obviously, you would also need the external address to your machine (www.domain-name.com).

But if you have installed it to a different folder, and created a virtual directory in IIS, lets say this is "DotNetNuke", then you would need "localhost/DotNetNuke" and "www.domain-name.com/DotNetNuke".

One way to explain it is this:
For every real address that you want people to use to access your website, you need to add this address as an Alias in your portal settings. Note that you do not need "localhost" as an alias, in order for people on the internet to access your website. "localhost" is just an address you can use from the webserver itself to access the site. You could instead add the machine's name to do the same thing. You must include your public address in order for people on the internet to reach your site. You can optionally add your static-IP-address (as Vanderland did), but this may not be desired, because then people may see your IP-address in their address-bar, instead of your pretty, public URL-address (as occurred on Vanderland's site). If in doubt, put your URL-address before any static-IP-address, because it should then default to the url-address first (at least it would if I was the one who programmed dotNetNuke). Don't quote me on that part though.