Skip to content
rakhesh.com

rakhesh.com

rakhesh sasidharan's mostly techie oh-so-purpley blog

  • Home
  • About
  • Quotes
  • Credits
  • Changelog
  • GitHub
  • X
  • LinkedIn
  • Mastodon (Hachyderm)
  • Mastodon (BSD Cafe)

Search

Subscribe via Feed

RSS | JSON

Categories

  • Asides (111)
  • Azure, Azure AD, Graph, M365 (194)
  • Books, Audiobooks, Podcasts (49)
  • Citrix (62)
  • Coding (32)
  • Docker (22)
  • Exchange, Exchange Online (49)
  • Gadgets (67)
  • Infrastructure (102)
  • Linux & BSD (66)
  • Mac (56)
  • Musings (52)
  • Networks (45)
  • Power Platform (26)
  • PowerShell (117)
  • TV, Movies, Music (72)
  • Virtualization (108)
  • Windows (271)
  • WordPress (11)

[Aside] Finding the source of a domain account lockout

An excellent post. Easy and to the point. Wish I had discovered this much before. The upshot is:

  • Enable debugging on a domain controller: nltest /dbflag:0x2080ffff
  • Disable debugging after a bit: nltest /dbflag:0x0
  • Check the logs at %windir%\debug\netlogon.log to find out where/ what is locking the account.
Posted on October 9, 2017October 9, 2017Author rakheshCategories Asides, Windows

Post navigation

Previous Previous post: [Aside] NetScaler and WireShark
Next Next post: MSI, MST, and disabling auto-healing/ self-repair/ “please wait while Windows configures” messages for certain applications