Hi,
Almost ready to use DNN for a real job but have a final issue I'd like to get straight in my head.
My setup as follows - Windows XP Home, Visual Web Developer 2005, SQL Express 2005
Installed everything to c:\dotnetnuke and am working on localhost only.
Accessed portal (let's call it MyFirstSite with an alias of localhost/dotnetnuke - cannot remember if I created this alias or it is done by default) through http://localhost/dotnetnuke fine - been using this for a few weeks just to get the hang of things.
I now want to add another parent portal (MySecondSite) for a totally unrelated subject. Created new portal called MySecondSite with an alias localhost/sitenumbertwo. When I open the browser and try to go to http://localhost/sitenumbertwo I get the Internet Exporer cannot display the webpage message.

Why does the first one work and not the second when everything else seems the same.
Should I just go to XP Pro, IIS and Visual Studio to stop all these problems or am I missing the point?

A final query - I'm hoping to have lots of different unrelated sites created using DNN which end users will content manage themselves. If one user manages to 'crash' their site would this cause all the others to stop functioning and therefore would it be safer for each site to have a fresh DNN installation. The sites could be just a few pages or many hundred.

Thanks very much for any guidance - can't wait to get my first site up and running,
relkeel

Creating new child portals on localhost is a bit tricky. Because you are already running in a virtual directory, you need to create the url like this: http://localhost/dotnetnuke/sitenumbertwo.

In a live environment, you would have set up your IIS to catch all trafic to a fixed IP address (so no hostheaders set up in IIS), then you can just point multiple domains to the same site. In dnn, you would create parent portals for the domain names

In my experience its rather difficult for customers to be crashing their site... you just need to keep monitoring site performance

DNN Blog | Twitter: @erikvb | LinkedIn:

Dan,

First question (I don't see it mentioned in your post) -- did you set up DNS for your subdomain? I mean is that URL pointing to your IP address? because after reading through your post it sounds as though it should be working if DNS is set up properly...

Ian