My winbindd and wb-ads short name logs in both 3.2.4 and 3.2.6 are
filled with this pattern:
[2008/12/27 23:19:16, 3] libsmb/cliconnect.c:cli_session_setup_spnego(880)
cli_session_setup_spnego: got a bad server principal, trying to guess ...
[2008/12/27 23:19:16, 3]
This simple and often-suggested command to test Samba:
getent passwd
reproducibly upsets winbindd on my SLES 10 SP1 machine. The command
does often return many results from our campus ADS. But after it
completes -- or if the command pauses for quite some time after
showing local users -- Samba
On Sun, Dec 14, 2008 at 8:52 AM, Lars Müller l...@samba.org wrote:
On Sat, Dec 13, 2008 at 09:12:53PM -0500, Frank Burleigh wrote:
My SuSE ES 10 SP1 (32bit) and SP2 (64bit) servers have (from the
opensuse repositories) Samba 3.2.4, with the MIT Kerberos provided in
the SLES distribution
My SuSE ES 10 SP1 (32bit) and SP2 (64bit) servers have (from the
opensuse repositories) Samba 3.2.4, with the MIT Kerberos provided in
the SLES distribution. In other words, my Samba is a little ahead
of the Kerberos distribution.
Is this a problem?
I ask because the winbindd log on the 64bit
We have Samba 3.2.4 on two SLES 10 (one is SP1, the other SP2 64bit)
machines. Both are member servers in our ADS, which was over the past
month given some additional DCs, new IPs for all DCs, and upgraded to
Windows 2008 (from win2003). The krb5.conf and nsswitch.conf files on
the two machines
