Hi, I am running Samba v3.0.14a-2 with winbindd on Fedora Core. smb.conf: auth methods = winbind winbind nested groups = Yes nsswitch.conf: passwd: files winbind ldap shadow: files ldap group: files winbind ldap The excessive logging started happening as soon as Service Pack 2 was installed on the win 2003 servers that are the domain controllers. Prior to the upgrade, the win 2003 servers were at Service Pack 1 with all hotfixes installed. Here is a random sample of the winbindd log: libads/ads_ldap.c:ads_sid_to_dn(222) ads sid_to_dn mapped CN=bschwar,OU=Students,OU=People,DC=catnet,DC=wfo,DC=linfield,DC=edu : 3 Time(s) libads/ads_ldap.c:ads_sid_to_dn(222) ads sid_to_dn mapped CN=bsmedle,OU=Students,OU=People,DC=catnet,DC=wfo,DC=linfield,DC=edu : 3 Time(s) libads/ads_ldap.c:ads_sid_to_dn(222) ads sid_to_dn mapped CN=chofmei,OU=Students,OU=People,DC=catnet,DC=wfo,DC=linfield,DC=edu : 2 Time(s) nsswitch/winbindd_ads.c:lookup_usergroups(632) ads lookup_usergroups for sid=S-1-5-21-487535032-342659857-1939201933-10480 : 1 Time(s) nsswitch/winbindd_ads.c:lookup_usergroups(632) ads lookup_usergroups for sid=S-1-5-21-487535032-342659857-1939201933-10549 : 1 Time(s) nsswitch/winbindd_ads.c:lookup_usergroups(632) ads lookup_usergroups for sid=S-1-5-21-487535032-342659857-1939201933-11197 : 1 Time(s) nsswitch/winbindd_ads.c:lookup_usergroups(632) ads lookup_usergroups for sid=S-1-5-21-487535032-342659857-1939201933-11198 : 3 Time(s) nsswitch/winbindd_ads.c:query_user(437) ads query_user gave mamason : 2 Time(s) nsswitch/winbindd_ads.c:query_user(437) ads query_user gave mcooper : 1 Time(s) nsswitch/winbindd_ads.c:query_user(437) ads query_user gave mmaebor : 2 Time(s) nsswitch/winbindd_group.c:winbindd_getgroups(1008) [27513]: getgroups CATNET\jolds : 3 Time(s) nsswitch/winbindd_group.c:winbindd_getgroups(1008) [27513]: getgroups CATNET\mcooper : 2 Time(s) nsswitch/winbindd_group.c:winbindd_getgroups(1008) [27513]: getgroups CATNET\mfa5165$ : 2 Time(s) None of the above entries look like an error that one would expect to see reported at log level 0. Any ideas? Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR