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 ForumsAuthenticationAuthenticationDNN AD Provider ConfigurationDNN AD Provider Configuration
Previous
 
Next
New Post
6/4/2009 12:47 PM
 

Dan's correct. On auto login the provider takes the LoggedOnUserName of whomever is logged onto the computer and tries to authenticate that user against the AD.

 
New Post
6/4/2009 1:41 PM
 

Thanks Mike and Dan. I followed what you said and added my test machine to the domain. I am now part of the domain and when I log into the workstation I should be on the domain now. But I still get a popup and when logging in as the domain user it still does not auto-login into DNN.

 
New Post
6/4/2009 11:53 PM
 

I'm starting to suspect it's something to do with Server 2008. What is different between IIS 7 on Server 2008 vs Vista I don't know and unfortunately I don't have a Server 2008 system to test on.

 
New Post
6/5/2009 7:36 AM
 

We need to take one step backwards in trouble-shooting first...

- When logging into the workstation, make sure you are logging in using a domain account, not a local-machine account.

- Since the IE settings are at the user level, any previous changes will not be there in the new domain account on that workstation, so make sure that the website is added back in as a trusted site or in the local Intranet group within IE.

If that still doesn't work, we'll start taking a closer look at the Windows 2008 Server.  I have several here on my network, but my main webserver is still on Windows 2003 R2, so I'd have to setup a test site see what is going on.

One thing I "can" say for sure is that by default W2K8 is locked down significantly more than W2K3 was.  For example, in W2K3 the firewall is disabled by default, while in W2K8 the firewall is enabled, bi-directional, and locked down tight.  You need to specify what programs are allowed to communicate with the network before a lot of things start working.  There is an advanced Firewall Settings menu where you can disable it temporarily, but off the top of my head I cannot recall how to get into it as it is not a normal menu item.   On the other hand, be careful of disabling the Firewall Service.  In W2K3/XP it was simple to test if communications problems were a firewall issue, as all you had to do was to stop the Firewall Service in the Services menu, but if you attempt the same thing in W2K8/Vista, it will actually shut down ALL network communications if you do that.

 

 

 
New Post
6/5/2009 6:53 PM
 

Thanks guys.

The main problem maybe the fact we have a Novell Client on our workstations and the userDLU is being the problem. I will have to test some things come this monday and see if the novell is the culprit. We have it setup where eDirecotry is talking to the AD and that my user is on the domain. I can map a domain drive without being prompted. But as you said it could be a local user thing as well so I will also look into that.

The 2008 server has been "dumbed" down. Firewall disabled and such.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationDNN AD Provider ConfigurationDNN AD Provider Configuration


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