Every few weeks users are not able to logon anymore until i restart the winbind daemon. The message in winbind.log is NT_STATUS_NO_LOGON_SERVERS. after that PAM (system-auth --> pam_succeed_if.so) is not able to resolve the active directory groups anymore. The quick fix is to create a new situation in our monitoring tool to restart the daemon if this message appears in the log. Is this a known problem? regards urs
Ok. it seems i am not the only one with this problem: http://www.mail-archive.com/samba@lists.samba.org/msg88996.html I did a "net ads lookup" and "net ads info" before and after the Problem occurred. The output (DC etc..) was exactly the same. I dont know much about our Microsoft ADS environment, but i know that the windows servers in that domain do not have this problem. I also have the impression that it happend much more often on our 64bit RHEL servers (with 64bit samba installed). **any help would be greatly appreciated! ---------- Forwarded message ---------- From: Urs Golla <urs.golla@gmail.com> Date: Thu, Nov 6, 2008 at 11:26 AM Subject: NT_STATUS_NO_LOGON_SERVERS To: samba@lists.samba.org Every few weeks users are not able to logon anymore until i restart the winbind daemon. The message in winbind.log is NT_STATUS_NO_LOGON_SERVERS. after that PAM (system-auth --> pam_succeed_if.so) is not able to resolve the active directory groups anymore. The quick fix is to create a new situation in our monitoring tool to restart the daemon if this message appears in the log. Is this a known problem? regards urs
On 11/11/2008 4:16 AM, Urs Golla wrote:> Ok. it seems i am not the only one with this problem: > http://www.mail-archive.com/samba@lists.samba.org/msg88996.html > > I did a "net ads lookup" and "net ads info" before and after the Problem > occurred. The output (DC etc..) was exactly the same. I dont know much about > our Microsoft ADS environment, but i know that the windows servers in that > domain do not have this problem. I also have the impression that it happend > much more often on our 64bit RHEL servers (with 64bit samba installed). > > **any help would be greatly appreciated!Is it asking too much for some basic evironemnet details? Like, maybe, Samba version? It really surprises me sometimes how many people seem to think list members are mind readers. -- Best regards, Charles
RPMS: samba3-winbind-3.0.28-35 samba3-utils-3.0.28-35 samba3-3.0.28-35 OS: Red Hat Enterprise Linux ES release 4 (Nahant Update 6) kernel: 2.6.9-67.0.1.ELsmp ADS: Microsoft Active Directory (Windows 2003 SP2, 32 and 64 bit), Domain Functional Level: Windows Server 2003, Forrest Functional Level: Windows Server 2003 The last 3 times it happened when the server was connected to our PDC. We have 22 domain controllers and I am almost sure it was always the PDC. Is it possible to blacklist a "bad" DC? On Tue, Nov 11, 2008 at 2:11 PM, Charles Marcus <CMarcus@media-brokers.com>wrote:> On 11/11/2008 4:16 AM, Urs Golla wrote: > > Ok. it seems i am not the only one with this problem: > > http://www.mail-archive.com/samba@lists.samba.org/msg88996.html > > > > I did a "net ads lookup" and "net ads info" before and after the Problem > > occurred. The output (DC etc..) was exactly the same. I dont know much > about > > our Microsoft ADS environment, but i know that the windows servers in > that > > domain do not have this problem. I also have the impression that it > happend > > much more often on our 64bit RHEL servers (with 64bit samba installed). > > > > **any help would be greatly appreciated! > > Is it asking too much for some basic evironemnet details? Like, maybe, > Samba version? > > It really surprises me sometimes how many people seem to think list > members are mind readers. > > -- > > Best regards, > > Charles > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >