Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationInstall Active Directory for beginners like me!Install Active Directory for beginners like me!
Previous
 
Next
New Post
9/6/2006 8:49 PM
 
I think this is because the users still exist in the ASPNET tables in SQL, specifically aspnet_users and aspnet_membership. You have to delete the lines in those for the user to join again but there is a specific sequence that must be followed when deleteing lines in the aspnet tables and I cannot remember what it is I had the same problem a while ago and found a post in the forums describing what to do and it worked for me.
 
New Post
9/7/2006 3:11 AM
 
Hello,

you have to delete the entry in aspnet_Membership and then in aspnet _users

Cedric
 
New Post
9/7/2006 9:51 PM
 
Thanks for the great tute. That has made the process much simpler for me.

In case anyone comes across some of the issues that I have:

Firstly, I found that the controls on the ADSI Authentication tab were disabled, and a warning that the web.config wasn't configured properly. I had no idea what wasn't configured properly, but eventually figured out that if i commented out:
<trust level="Medium" originUrl="http://localhost/.*" />
the controls would be enabled. (This could be something do do with my local config)

Secondly, I had trouble getting the system to see my domain. My workstation (XP Pro, IIS) is a member of the domain and login worked ok, but the ADSI auth tab would give me several fails when I clicked on update. So I moved the site to a member server (Win Server 2003, IIS6) and immediately it's working happily. One possibility is that this has to do with windows firewall, but group policy means I can't turn it off to check.

Now I'm at the stage that it works ok, domain users can log in (on either site), but I can't administer the users. When I try to view users in Admin > User Accounts, I get a module load exception... Object reference not set to an instance of an object etc etc.
If I try to Admin > Security Roles, I can see the user accounts, but the names are blank (except for the usual DNN admin account).

If anyone has seen this, it'd be great to hear from you. I'll keep trying to find the answer and post it here when I have it.
 
New Post
11/1/2006 6:09 AM
 
Excellent walkthrough, finally got it working now! Only thing which is tobad is that you have to do some settings on the client to auto-login
 
New Post
11/1/2006 10:46 AM
 

RutgerB wrote
Excellent walkthrough, finally got it working now! Only thing which is tobad is that you have to do some settings on the client to auto-login

If you have access to AD, then you can create a policy to force all of your Intranet computers to recognize your domain as being in the "Intranet Zone" in IE.  That will keep you from having to change each computer manually (saved me a heck of a lot of work with 1200+ computers!).

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationInstall Active Directory for beginners like me!Install Active Directory for beginners like me!


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out