NLTest on DC: "ERROR_NO_LOGON_SERVERS"



  • I happened to be backing up the netlogon logs from our domain controllers when I noticed an issue from one of our DCs. When I run "nltest /query" from a CMD prompt, I get the following results:

    Flags: 0
    Connection Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
    The command completed successfully

    I verified the other 5 DCs and the command returns 0x0 NERR_Success on all of them except for this one.

    I tried restarting the Netlogon service, but the error persisted. I then did a reboot of the server, and tested again after it came back up; the results were 0x0 NERR_Success. I noticed that the log file had more info than I wanted to see (I normally only want to see info like this: 10/13 06:16:37 LAKEIMAGING: NO_CLIENT_SITE: 3RD-HR2 192.168.210.250); there was way more verbosity than that. So I ran "nltest /dbflag:0x0" and restarted the netlogon service. Afterwards, I tested again with "nltest /query" and I am getting the same error as before (1311)!! I can't figure out what is causing this or how to fix it permanently!



  • Maybe my google-fu is good enough?

    One microsoft "of go read this" and another topic of "check your ports"



  • @DustinB3403 said in NLTest on DC: "ERROR_NO_LOGON_SERVERS":

    Maybe my google-fu is good enough?

    One microsoft "of go read this" and another topic of "check your ports"

    I don't see any Event ID 11 messages in my System log, so that rules out that issue at least.

    I noticed that the firewall was turned on, so I turned that off! (We don't have it "on" on any of our other DCs). I rebooted and ran the test again and got Connection Status = 0 0x0 NERR_Success. I was expecting to after a reboot (just like last time), so I'll wait at least 60 minutes and test again to see if I still get "success".

    I'll report back later this afternoon! 🙂



  • Everything is still looking good!