Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Samba] NETLOGON failure

250 views
Skip to first unread message

Viktor Trojanovic

unread,
Nov 22, 2015, 8:20:03 AM11/22/15
to
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

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

mourik jan c heupink

unread,
Nov 23, 2015, 11:30:07 AM11/23/15
to
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

Rowland Penny

unread,
Nov 23, 2015, 11:50:04 AM11/23/15
to
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

mourik jan c heupink

unread,
Nov 23, 2015, 12:10:03 PM11/23/15
to
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... :-)

Viktor Trojanovic

unread,
Nov 23, 2015, 5:10:03 PM11/23/15
to


On 23.11.2015 17:58, mourik jan c heupink wrote:
> 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... :-)
>
Thanks MJ for bumbing the thread, and thanks Rowland for the solution.
I've gotten so used to add the term "Samba" in my searches when looking
for a windows AD problem that naturally I missed this link.

Viktor
0 new messages