Yes, i am a newbe, though with a week under my belt on dnn6 and even having created my own db modules i have some understanding of dnn.  but there is a mystery here for me - not in creating a new portal but in making use of it.  i created both an empty portal and one using the default template but cannot access them as the new administrator.

setup:
 new parent portal in 
    testbox.mydomain.com

 since i deleted one and tried again, under   /dotnetnuke6/Portals/2/
 there are these subdirs:
    /cache
    /images
    /templates
    /users
    logo.png
    portal.css

within /templates i do have file Default.page.template

however, it beats me how to get in???   or, how do i expand that default template within the new portal??  i have tried logging in to my _default site with the new administrator and have no luck. 
did something go wrong?  if so, it happened to both new portal installations.

i know people must get around this every day but i am missing something,
thanks in advance!

hey!   thanks for the quick response...

partly my bad here, but something is still bunged.
i made another domain, lets call it testsandbox.mydomain.com
and this one i pointed to the dnn install dir  /dotnetnuke6  -- something i should have noticed -- oops
and i made a new portal which used testsandbox.mydomain.com for a parent

Now, this does give me a login page so it is progress.  yea! 

but, the admin i created for testsandbox.mydomain.com does NOT work.  the superuser and administrator for the default DO work in this domain -- which does not seem right  -- and another screwball thing is that when these do log in, they redirect to the "main" domain of www.mydomain.com which displays the ancient existing home page in the dnn login window – a very weird sight.

regarding
>> try logging in as host and going to host->portals and then selecting your portal there (but really the URL should work -did you add the necessary host header in IIS for it?)

hmmm,
i understand logging as host, but this is hosted on - godaddy – which is the “one button click” king – so I haven’t even seen the iis console and am not sure what the host header for iis should be or where to find it.  sorry...  may not be part of the issue here...

so, if there is anything to cull from the above, it is that the portal did install in my intended domain, but the administrator for that domain cannot log in.  i would like to see it work properly from the start before continuing

again, thanks for the help!

it looks like you've done the DotNetNuke steps right but not the IIS steps - IIS needs to know that a domain is intended for a website so brand new domains need to be set up as host headers -e.g. http://www.dotnetscraps.com/dotnetscraps/post/Did-you-know-Add-host-header-to-a-Web-Site-in-IIS-7-IIS-75.aspx . This is not something we can do from DotNetNuke, it's a step you need to do manually. Note: this only applies to new parent portals, child portals do not require this setup as they are folders off an existing domain.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US