Ah, thanks, didn't even realize 3.0.31 had been released. I'll give that a try.
-HKS On Tue, Jul 15, 2008 at 6:15 PM, Jeremy Allison <[EMAIL PROTECTED]> wrote: > On Tue, Jul 15, 2008 at 06:12:41PM -0400, (private) HKS wrote: >> I was finally able to correct these errors by enabling Kerberos >> and changing the security model from domain to ads, but now >> I've run into the same problem reported here: >> http://www.usenet-forums.com/samba/394092-re-samba-accessing-member-server-prompts-credentials.html >> >> After about 5 minutes of uptime the winbind service throws >> several errors into syslog and nothing referencing it will work >> correctly until I restart it. The processes are still running. >> >> Jul 15 17:57:26 testbox winbindd[994]: [2008/07/15 17:57:26, 0] >> nsswitch/winbindd_dual.c:async_request_timeout_handler(182) >> Jul 15 17:57:26 testbox kernel: Jul 15 17:57:26 testbox winbindd[994]: >> [2008/07/15 17:57:26, 0] >> nsswitch/winbindd_dual.c:async_request_timeout_handler(182) >> Jul 15 17:57:26 testbox winbindd[994]: >> async_request_timeout_handler: child pid 992 is not responding. >> Closing connection to it. >> Jul 15 17:57:26 testbox kernel: Jul 15 17:57:26 testbox winbindd[994]: >> async_request_timeout_handler: child pid 992 is not responding. >> Closing connection to it. >> >> This is Samba 3.0.30 and Kerberos 5 running on FreeBSD 7.0. >> >> Can anyone help me out here? > > Known bug that was explicitly fixed in 3.0.31. > > Jeremy.
