Testing 3.6.0 on a member server of a 3.5.8 domain shows some strange problems.
With the standard:
idmap config * : backend = tdb
no results are returned by getent, and wbinfo does not always
work, also no winbind_idmap.tdb file is ever created.
by changing to:
idmap config * : backend = rid
or
idmap config * : backend = hash
results are obtained but are the same regardless of range (or base_rid).
Am 12.08.2011 16:25, schrieb Chris Smith:> Testing 3.6.0 on a member server of a 3.5.8 domain shows some strange problems. > > With the standard: > idmap config * : backend = tdb > > no results are returned by getent, and wbinfo does not always > work, also no winbind_idmap.tdb file is ever created.Same here (just with a 3.5.11 PDC). https://bugzilla.samba.org/show_bug.cgi?id=8371 Do you see the "bad packet" messages also on your PDCs nmbd.log when wbinfo tries to fetch information?
On Fri, Aug 12, 2011 at 10:30 AM, Marc Muehlfeld <Marc.Muehlfeld at medizinische-genetik.de> wrote:> Do you see the "bad packet" messages also on your PDCs nmbd.log when wbinfo > tries to fetch information?Yes, but not 100% correlated. IOW, there are some, but there should be more with all of the attempts I made. Chris
On Fri, Aug 12, 2011 at 10:25 AM, Chris Smith <smb_77 at chrissmith.org> wrote:> With the standard: > ?idmap config * : backend = tdb > > ? ?no results are returned by getent, and wbinfo does not always > work, also no winbind_idmap.tdb file is ever created. > > by changing to: > ?idmap config * : backend = rid > or > ?idmap config * : backend = hash > > ? ?results are obtained but are the same regardless of range (or base_rid).Turns out that sometimes (during various restarts) results will be obtained with: idmap config * : backend = tdb However, as previously noted, no winbind_idmap.tdb file is created and the results are always the same. Basically the "idmap config" settings seem to have no effect, regardless of type (tdb, rid, hash) or range the result for 'getent passwd' (when I get one) is always: TESTDOMAIN\root:*:322438120:322437633:root:/home/TESTDOMAIN/root:/bin/false TESTDOMAIN\me:*:322438122:322437633::/home/TESTDOMAIN/me:/bin/false TESTDOMAIN\you:*:322438123:322437633::/home/TESTDOMAIN/you:/bin/false TESTDOMAIN\test:*:322438126:322437633::/home/TESTDOMAIN/test:/bin/false Chris
` Chris Smith wrote:> Testing 3.6.0 on a member server of a 3.5.8 domain shows some strange problems. > > With the standard: > idmap config * : backend = tdb > > no results are returned by getent, and wbinfo does not always > work, also no winbind_idmap.tdb file is ever created. > > by changing to: > idmap config * : backend = rid > or > idmap config * : backend = hash > > results are obtained but are the same regardless of range (or base_rid). >Yeah...reported this a month ago... as well as other TDB/SID backend probs: http://lists.samba.org/archive/samba-technical/2011-July/078663.html http://lists.samba.org/archive/samba-technical/2011-July/078826.html --- I wasn't sure if it was a 3.6 problem or some type of cockpit error, but both emails were ignored. -- so the problem was known about nearly a month ago, but my input wasn't considered valid without "knowing what the problem was"... Had one case that I found that gave corrupted packets that I could show in a trace. That one got fixed... But w/out hard details, they are busy folk...