I am having the same problem with two intalls of DNN

One is server 2003 with SQL 2005 iis no idea probably 6 DNN 4.3.0

I have installed DNN as a virtual directory at the same level as the www root on the server

X:\XXX\wwwroot         -    

X:\XXX\dotnetnuke - this is a virtual directory

I try to create the new portal in  - X:\XXX\MyNew Portal - I have tried with and without mapping this as a Virtual directory under the web root 

so access is :    www.abc.com/dotnetnuke

the other is xp pro SQL 2005 iis 5.1 DNN 4.3.2

here the  DNN folder is set as a virtual directory within the Virtual directory that represents the web root

C:\ASPNET\DotNetNuke  = Virtual Dir under webroot

C:\ASPNET\DotNetNuke\Portals\MyNewPortal

so access is : localhost/dotnetnuke

I log in as host and create a portal - Or try to

Without the directory for the portal it just switches to "page not found"

With the direcotry created manually is switches to a blank screen or the browser tries to browse the directory

I have tried many variations most of which state the portal is created but I am unable to acces it either by  typing in the url or alias in the browser

if the Portal  isnt created it states the user already exists despite using the same password etc (as described in other posts on this forum)

Once It seemed the directory was populated with the pictures for the template file ( i use the small business set up so the musical instrument pics appeared)

 I have tried logging in as the admin user but i just get the error about password case sensitivity

I have looked through the database and cleared the users out ( again mentioned elsewhere - surely there should be a module or utility to tidy up the Database to avoid this sort of redundant data being left on the DB - Once I make progress past this basic level I will be looking at coding one if there isnt one already)

Oh yes I am trying to set up a parent portal so others on this team can use dnn ( i.e I want to create a portal that can create other portals)

any suggestions gratefully recieved even if to point out my oversight of documentation etc - I am sure its me as the behaviour is the same in both cases

Dave

Lummers,

Have you tried creating a "Child" portal and then adding the new http alias for a parent portal?  Make sure the parent.mysite.com is also available in IIS.

Here is what I do to create a new parent portal, keeping in mind that I also want all of my sites available at mysite/theirsite.com. The only thing done at the server level here is adding the domain to the site in IIS, the rest is done right throught the Admin or Host menus via DNN.

1. Host > Portals > Add New Portal
2. Select Child (mysite/newsite.com)
3. Change directory to Portals/newsite.com (This makes it much eaisier to do housekeeping via FTP)
4. Complete the balance of the information and "Create Portal"
5. Go to IIS and in site properties Add www.newsite.com (or newsite.mysite.com)
6. Back in IE you should be at mysite/newsite.com
7. Admin > Site Settings > Add New Alias
8. Add www.newsite.com (or newsite.mysite.com) as alias.

Thats it, providing all of the DNS information for the newsite domain is correct you should be all set.