First, a comment: I only use one Portal, the one that is set up during Install. In the directory structure of the site it is Portal 0. That portal has exactly the same losing authenticaion problem in IE that everyone else is reporting on this thread. I have verified this on the following clients:
Win XP Pro SP2+, .NET 2.x, IE 6.0.2900.2180 SP 2
Win 98 (not SE or ME, but fully patched), .NET 1.x, IE 6.0.2900.???? I forget, but it is fully patched.
My server is:
Brinkster - Win 2003, .NET 2.x, SQL 2000, DNN 4.0.2
URL:
http://ionearth.com/default.aspx (http://ionearth.com just goes to the live site which is mostly flat HTML)
I've read this entire thread and tried all the suggestions that seem to apply...except the parent portal trick.
I have been working with, developing for, LAMP Open Source projects for years. But, because I am somewhat new to .NET, and completely new to DNN and just got everything the way I want it, I haven't tried re-creating (copying?) my existing portal as a parent portal.
Thanks to the posts here I think I will have enough clues to do this, if I must.
There is no explicit setting that tells me if an existing portal is a parent or child, but I went through the create portal process far enough to see that there IS an explicit option to force a parent portal to be created....
My question: Before I muck around with my host creating additional portals....how can I determine for certain if my existing portal is a child or a parent?
Any help is welcome.
- John
IonEarth Lead Web Developer