DNN v3.2.2

The Last Login Date does not seem to be changing after a user is sucesssfully authenticated.
The Last Login Date seems to stay fixed on the date the account was created.

We are running in mixed mode.  Logging in with a non AD account changes the Last Login Date.

What is everyone else seeing?

thanks,

mikez

Logged into bug tracker.

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=2317

Hi,

the code isn't the problem. In nt/2000 domains the timestamp was the last time the user logged on to the PDC or BDC. So  you'd have to query every domain controller in the domain, this wasn't practical.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ad/ad/attributes.asp

Non-replicated attributes, such as badPwdCount, Last-Logon, and Last-Logoff are stored on each domain controller, but are not replicated. The non-replicated attributes are attributes that pertain to a particular domain controller. For example, Last-Logon attribute is the last date and time that the user's network logon was validated by that particular domain controller that returned the property. These attributes can be retrieved in the same way as the domain-wide attributes described previously. However, for these attributes, each domain controller stores only values that pertain to that particular domain controller. For example, to obtain the last time that a user logged on to the domain, retrieve the Last-Logon attribute for the user from every domain controller in the domain and find that latest date and time.

The solution:

http://www.ondotnet.com/pub/a/dotnet/excerpt/ADcookbook_chap1/?page=2

Only for 2003 se3rver :(

Regards Ángel.