Thanks Mike for your prompt reply. It sounds interesting this IP range (or Subnet) functionality your mentioning. So we will have to wait till this is released. Till then we will that you are suggesting above this will for sure cover the requirement till the next module release.

Thanks,

Antonis

"The commented out line is from the old provider. When the new one is installed it'll automatically add the correct line at the bottom of the httpModules section so I'm guessing you might have two lines with the same info in them. That may be part of the problem. As for the failures and info not being added to the DNN profile you may have to use impersonation on the site. Look for the commented out section in your web.config that starts <identity impersonate="true"/>. Uncomment that line only and change it so that it looks like <identity impersonate="true" userName="domain\username" password="password" />. The user you use in that line will have to have the same rights to your DNN folder that NETWORK SERVICE has.

I'm just waiting for someone on the core team to release the code here on DNN but if you want it you can find it on my website http://dnn.gmss.org."

---

Actually it is working fine now.  I thought they would've updated the web.config to use the new provider but I guess not.  I don't have two lines, I commented out the old one and inserted the one from your blog post.

"I'm just waiting for someone on the core team to release the code here on DNN but if you want it you can find it on my website http://dnn.gmss.org."

---

Thanks but I really need the source for DotNetNuke.Authentication.ActiveDirectory.dll and your source doesn't seem to include it.