I've had samba working on a number of servers (8.04) within an active directory domain for years but I've been struggling with a problem that started a few months ago. I also have the same problems on 10.04 servers.
Essentially, after a certain number of users have logged in, winbind falls over and has to be restarted before the latest users can access shares. I'm certain it has something to do with dhcp leases but that could be a red herring.
I don't know what could have changed, config wise, to cause this. I use pfsense to hand out ip addresses and act as dns server. DNS resolution works. Reverting back to using the dns and dhcp on the Win2k3 server doesn't help.
A typical log entry is...
[2010/07/23 07:25:55, 1] nsswitch/winbindd_ads.c:ads_cached_connection(12
ads_connect for domain <MYDOMAIN> failed: No logon servers
but I also get entries like...
[2010/07/20 08:17:09, 1] nsswitch/winbindd_group.c:fill_grent_mem(365)
could not lookup membership for group sid S-1-5-21-2000478354-527237240-1801674531-512 in domain <MYDOMAIN> (error: NT_STATUS_UNSUCCESSFUL)
This is frustrating because I'm getting phone calls in the evenings and on weekends to restart the winbind daemons. A cron job to restart them every hour or so doesn't help because the problem manifests during a logon when the drives are mapped.
I'd be most grateful for any suggestions.
Essentially, after a certain number of users have logged in, winbind falls over and has to be restarted before the latest users can access shares. I'm certain it has something to do with dhcp leases but that could be a red herring.
I don't know what could have changed, config wise, to cause this. I use pfsense to hand out ip addresses and act as dns server. DNS resolution works. Reverting back to using the dns and dhcp on the Win2k3 server doesn't help.
A typical log entry is...
[2010/07/23 07:25:55, 1] nsswitch/winbindd_ads.c:ads_cached_connection(12
ads_connect for domain <MYDOMAIN> failed: No logon servers
but I also get entries like...
[2010/07/20 08:17:09, 1] nsswitch/winbindd_group.c:fill_grent_mem(365)
could not lookup membership for group sid S-1-5-21-2000478354-527237240-1801674531-512 in domain <MYDOMAIN> (error: NT_STATUS_UNSUCCESSFUL)
This is frustrating because I'm getting phone calls in the evenings and on weekends to restart the winbind daemons. A cron job to restart them every hour or so doesn't help because the problem manifests during a logon when the drives are mapped.
I'd be most grateful for any suggestions.