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 ForumsAuthenticationAuthenticationWindows Authentication is Currently Unavailable Error in DNN 4.02 W2k3 ServerWindows Authentication is Currently Unavailable Error in DNN 4.02 W2k3 Server
Previous
 
Next
New Post
4/25/2006 12:01 PM
 

I know this helps on-one either but I going to go ahead and mention this anyways! I've faced this exact same problem - I was trying to switch between two ADs and while it worked fine in the first when I tried pointing to another one it kept giving this exact same error.

What was peculiar however was that once I got this error moving to the first AD (which worked fine previously) also started returning this error!

I wanted to revert back to my previous settings and it just wouldn't work! So here's what I did -

1. Restarted my IIS

2. Entered all old settings

(No Help - it gave the same exception)

1. Restarted the IIS

2. Entered all old settings with a wrong password (it gave a sensible error)

3. Entered correct password - and it worked!

I know this is bad debugging also reffered to as "debugging by co-incidence" :) but without the source code at hand - this is only so far I've been able to reach.

Hope this helps someone!

 
New Post
5/15/2006 10:32 PM
 

I have the same error(Object reference not set to an instance of an object. at DotNetNuke.Security.Authentication.ADSI.Utilities.AddADSIPath...cmdAuthenticationUpdate_Click) on our testing machine running XP Professional, when it works fine on development server with Windows 2003.
I think that it is related to security settings of  account running ASP.NET and access to AD, but didn't found the reason.

Does anyone found the solution?


Michael Freidgeim http://geekswithblogs.net/mnf
 
New Post
6/20/2006 5:20 AM
 

I have the same problem in dotnetnuke 4.3.0.

If I change trust level to Full and <identity impersonate="true"/>, the authentication form become available. But just admin, host, and my domain login can enter into. And I dont see my login name.

From web.config:

<trust level="Full" originUrl="http://localhost/.*" />

 

<!-- Forms or Windows authentication -->

<authentication mode="Forms">

<forms name=".DOTNETNUKE" protection="All" timeout="60" />

</authentication>

<!--authentication mode="Windows">

</authentication-->

<identity impersonate="true"/>

No one in our domain can enter into.

Error message:

//////////////////////////////////////////////

Unhandled Error

Error Details

File

 

Error  

Login failed for user 'domain\user'.

 
/////////////////////////////////////////////////////////////////////////////////////

Tam what do you think about it?

Does anyone found the solution?

 
New Post
8/17/2006 3:29 PM
 

Has anyone come up with a solution for this?  I have a fresh install of DNN 4.3.4 and am getting the same error.  But it only seems to occur when I use the "DC=mydomainname, DC=org" format.  If I change it to "mydomainname.org" and click update, I get:

Accessing Global Catalog:
FAIL
Checking Root Domain:
OK
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password.

Any assistance would be greatly appreciated.  We are in the process of review viable solutions for resigning our inhouse hospital software in the .NET suite.  DNN would provide us with the ability to focus our efforts on business logic, which is extensive in the healthcare industry, instead of Web design.

Thanks,
Steve
 
New Post
11/30/2006 2:13 PM
 

I'm getting the same error on our win2k3 box.  The first time I configured DNN as per the directions, update on the auth page showed it was accessing ADSI ok.  Browsing to the website greeted me with an IIS prompt for credentials. 

I changed to the  "DC=mydomainname, DC=org" and started getting the "Error: Windows Authentication is currently unavailable." message.

Setting root to "mydomainname.org" caused an Accessing Global Catalog: FAIL message.


 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationWindows Authentication is Currently Unavailable Error in DNN 4.02 W2k3 ServerWindows Authentication is Currently Unavailable Error in DNN 4.02 W2k3 Server


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