Displaying 5 results from an estimated 5 matches for "xxx_01".
Did you mean:
xxx101
2016 Feb 01
2
winbind warnings filling up syslog
Every few minutes windbindd posts an error message like:
winbindd: ../source3/libads/ldap.c:552(ads_find_dc)
winbindd: ads_find_dc: name resolution for realm 'XXX.CO'
(domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS
where XXX.CO is the domain name of a company my company
recently acquired and XXX_01 seems to be like they name of
the DCs around here.
I'm assuming winbindd is looking this up on the AD, even
though I have realm/default realm configured in smb.conf,
k...
2016 Feb 01
2
winbind warnings filling up syslog
hasm> Every few minutes windbindd posts an error message like:
hasm> winbindd: ../source3/libads/ldap.c:552(ads_find_dc)
hasm> winbindd: ads_find_dc: name resolution for realm 'XXX.CO'
hasm> (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS
hasm> How can I shut this thing up? I've also seen, not sure
hasm> whether related, winbindd shooting up to 100% CPU (of this
hasm> dual core box.)
rpenny> How are you running Samba ?
Fedora 23 daily patched.
Samba is enabled and started b...
2016 Feb 01
2
winbind warnings filling up syslog
...it showed up.
rpenny> In which case, you could try turning winbind off
I stopped and disabled sssd instead, then restarted smb,
nmb, winbind, and already have a couple of winbindd warning
lines in the logs:
winbindd: ads_find_dc: name resolution for realm 'XXX.CO'
(domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS
-- HASM
2016 Feb 01
0
winbind warnings filling up syslog
...case, you could try turning winbind off
>
> I stopped and disabled sssd instead, then restarted smb,
> nmb, winbind, and already have a couple of winbindd warning
> lines in the logs:
>
> winbindd: ads_find_dc: name resolution for realm 'XXX.CO'
> (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS
>
> -- HASM
>
Is firewalld running ?
Rowland
2016 Feb 01
0
winbind warnings filling up syslog
On 01/02/16 16:24, HASM wrote:
> hasm> Every few minutes windbindd posts an error message like:
> hasm> winbindd: ../source3/libads/ldap.c:552(ads_find_dc)
> hasm> winbindd: ads_find_dc: name resolution for realm 'XXX.CO'
> hasm> (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS
> hasm> How can I shut this thing up? I've also seen, not sure
> hasm> whether related, winbindd shooting up to 100% CPU (of this
> hasm> dual core box.)
>
> rpenny> How are you running Samba ?
>
> Fedora 23 daily patche...