So am i. What i dont understand is that i have about 12 .NET applications running on the same 2 servers, used for our (Super) users to handle different tasks in AD, ie. reset passwords, move users from one group to another ect.

Iv always had this problem with DNN only in the past this endless loop was only if the user was unknown in the database. Now its with everyone. It seems to be another problem though, as when i did debug in the past, in visual studio i could see it was something when cashing ending in a endless loop.

Iv spend weeks on this now, and must admit iv come to the conclusion, that it might be a group policy on our servers preventing DNN access to what ever it wants. It still seems to be some cashing (When debugging) when the ad-provider is switched on.

Iv followed your documentation on how to set it up, in each DNN installation iv used for test, and iv tried the tips and tricks iv seen posted in the forums, but nada.

Ill do some more tests, and hopefully come up with a solution