Hi list, Checking the Windows event logs, I see that my clients regularly complain a netlogon failure: Event 5719, NETLOGON This computer was not able to set up a secure session with a domain controller in domain SAMDOM due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. Unless I'm missing something, this message doesn't seem to have any impact on me as all seems to work as expected (DNS, NTP, GPO etc). Also, there are no logs whatsoever with regards to this error on the DC. Do others of you face a similar error message? Is this something that can safely be ignored? My config: Samba 4.3.1, Standard single AD DC config as per Samba wiki, internal DNS, Win10 clients
Hi Victor, I am sorry to see that you have received no replies at all. I am following your question with great interest, as we see the same errors in our eventlog. You are not alone. :-) I would like to know more about it as well. MJ On 22-11-2015 14:11, Viktor Trojanovic wrote:> Hi list, > > Checking the Windows event logs, I see that my clients regularly > complain a netlogon failure: > > Event 5719, NETLOGON > This computer was not able to set up a secure session with a domain > controller in domain SAMDOM due to the following: > There are currently no logon servers available to service the logon request. > This may lead to authentication problems. Make sure that this computer > is connected to the network. If the problem persists, please contact > your domain administrator. > > Unless I'm missing something, this message doesn't seem to have any > impact on me as all seems to work as expected (DNS, NTP, GPO etc). > Also, there are no logs whatsoever with regards to this error on the > DC. > > Do others of you face a similar error message? Is this something that > can safely be ignored? > > My config: Samba 4.3.1, Standard single AD DC config as per Samba > wiki, internal DNS, Win10 clients >
On 22/11/15 13:11, Viktor Trojanovic wrote:> Hi list, > > Checking the Windows event logs, I see that my clients regularly > complain a netlogon failure: > > Event 5719, NETLOGON > This computer was not able to set up a secure session with a domain > controller in domain SAMDOM due to the following: > There are currently no logon servers available to service the logon request. > This may lead to authentication problems. Make sure that this computer > is connected to the network. If the problem persists, please contact > your domain administrator. > > Unless I'm missing something, this message doesn't seem to have any > impact on me as all seems to work as expected (DNS, NTP, GPO etc). > Also, there are no logs whatsoever with regards to this error on the > DC. > > Do others of you face a similar error message? Is this something that > can safely be ignored? > > My config: Samba 4.3.1, Standard single AD DC config as per Samba > wiki, internal DNS, Win10 clients >Are you sure this is a Samba problem, I only ask this because a quick google brings up lots of results like this: https://support.microsoft.com/en-us/kb/2459530 Where it is very clearly a windows problem, so much so, that there is a hotfix available. Rowland
Hi Rowland,> Are you sure this is a Samba problem, I only ask this because a quick > google brings up lots of results like this: > > https://support.microsoft.com/en-us/kb/2459530 > > Where it is very clearly a windows problem, so much so, that there is a > hotfix available.Reading that page, it seems like exactly the issue we're seeing: both Netlogon event ID 5719 and Group Policy event ID 1129. I too assumed it was a samba thing, but thanks for using google for us... :-)