search for: fromidmap

...00(agroup) groups=10000(agroup),10007(othergroup) >> > Been having this issue on an dc after i updated from 4.1 to 4.2. It turned > out some users with defined uid also had mappings from winbind in idmap.tdb. > At firt the uid attributre gets used but afetr a while the value > fromidmap.tdb was used. The fix was to delete the mappings in idmap.tdb. > On an member server you can use net idmap set/get/dump to test this. As the problem was getting worse and worse on my end (UIDs resetting after a few minutes, mostly in response to SMB traffic), I did something similar: - stop...

...DC and > > this problem never happened then. > > > Been having this issue on an dc after i updated from 4.1 to 4.2. It > turned out some users with defined uid also had mappings from winbind > in idmap.tdb. At firt the uid attributre gets used but afetr a while > the value fromidmap.tdb was used. The fix was to delete the mappings > in idmap.tdb. > On an member server you can use net idmap set/get/dump to test this. > You are missing the fact that the OP is using the REALM name instead of the NETBios domain name and for some reason winbind is starting to allocate th...

...ed then. > >>> > >> Been having this issue on an dc after i updated from 4.1 to 4.2. It > >> turned out some users with defined uid also had mappings from > >> winbind in idmap.tdb. At firt the uid attributre gets used but > >> afetr a while the value fromidmap.tdb was used. The fix was to > >> delete the mappings in idmap.tdb. > >> On an member server you can use net idmap set/get/dump to test > >> this. > >> > > You are missing the fact that the OP is using the REALM name > > instead of the NETBios domain...

Hi all, I've been experiencing an intermittent problem where some UIDs on a member server spontaneously change from being their AD-derived values to being allocated from the default idmap space, even when there is no change to the AD user information. Specifically, I have a member server running Samba 4.4.5 on CentOS 6.8. AD service is provided by two Samba 4.4.5 servers. The member

...is member server was also a DC and > this problem never happened then. > Been having this issue on an dc after i updated from 4.1 to 4.2. It turned out some users with defined uid also had mappings from winbind in idmap.tdb. At firt the uid attributre gets used but afetr a while the value fromidmap.tdb was used. The fix was to delete the mappings in idmap.tdb. On an member server you can use net idmap set/get/dump to test this.

...0000(agroup),10007(othergroup) >>> >> Been having this issue on an dc after i updated from 4.1 to 4.2. It >> turned out some users with defined uid also had mappings from winbind >> in idmap.tdb. At firt the uid attributre gets used but afetr a while >> the value fromidmap.tdb was used. The fix was to delete the mappings >> in idmap.tdb. >> On an member server you can use net idmap set/get/dump to test this. > > As the problem was getting worse and worse on my end (UIDs resetting > after a few minutes, mostly in response to SMB traffic), I did...

...this problem never happened then. >>> >> Been having this issue on an dc after i updated from 4.1 to 4.2. It >> turned out some users with defined uid also had mappings from winbind >> in idmap.tdb. At firt the uid attributre gets used but afetr a while >> the value fromidmap.tdb was used. The fix was to delete the mappings >> in idmap.tdb. >> On an member server you can use net idmap set/get/dump to test this. >> > You are missing the fact that the OP is using the REALM name instead of > the NETBios domain name and for some reason winbind is sta...

...>>>> Been having this issue on an dc after i updated from 4.1 to 4.2. > >>>> It turned out some users with defined uid also had mappings from > >>>> winbind in idmap.tdb. At firt the uid attributre gets used but > >>>> afetr a while the value fromidmap.tdb was used. The fix was to > >>>> delete the mappings in idmap.tdb. > >>>> On an member server you can use net idmap set/get/dump to test > >>>> this. > >>>> > >>> You are missing the fact that the OP is using the REALM name...

...t;>>> >>>> Been having this issue on an dc after i updated from 4.1 to 4.2. It >>>> turned out some users with defined uid also had mappings from >>>> winbind in idmap.tdb. At firt the uid attributre gets used but >>>> afetr a while the value fromidmap.tdb was used. The fix was to >>>> delete the mappings in idmap.tdb. >>>> On an member server you can use net idmap set/get/dump to test >>>> this. >>>> >>> You are missing the fact that the OP is using the REALM name >>> instead of t...

...gt;> Been having this issue on an dc after i updated from 4.1 to 4.2. >>>>>> It turned out some users with defined uid also had mappings from >>>>>> winbind in idmap.tdb. At firt the uid attributre gets used but >>>>>> afetr a while the value fromidmap.tdb was used. The fix was to >>>>>> delete the mappings in idmap.tdb. >>>>>> On an member server you can use net idmap set/get/dump to test >>>>>> this. >>>>>> >>>>> You are missing the fact that the OP is using...