search for: pubserver64

...e[ 0]: SeChangeNotifyPrivilege Rights (0x 400): Right[ 0]: SeRemoteInteractiveLogonRight $ ldapsearch -H ldaps://dc2.ads.darkdragon.lan -b 'DC=ads,DC=darkdragon,DC=lan' '(&(objectclass=person)(objectSid=S-1-5-21-2269650170-3990761244-2407083512-1124))' # pubserver64, Computers, ads.darkdragon.lan dn: CN=pubserver64,CN=Computers,DC=ads,DC=darkdragon,DC=lan objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user objectClass: computer cn: pubserver64 instanceType: 4 whenCreated: 20180218050559.0Z uSNCreated: 3347 name: pubserver64...

On Thu, 2023-06-08 at 13:41 +0300, Andrey Repin via samba wrote: > Greetings, All! > > I've added a new DC to the working AD, transferred FSMO roles > (checked, all 7 > are ok') and (supposedly) correctly demoted the old DC. > > SchemaMasterRole owner: CN=NTDS > Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN= > InfrastructureMasterRole owner:

...t; domain computers:x:10003: domain sudoers:x:10006: domain admins:x:10000: domain guests:x:10002: cloud admins:x:10010: domain users:x:10001: remote users:x:10009: cloud users:x:10008: git admins:x:10007: cvs:x:10005: Even wbinfo lists groups/users incorrectly on different machines. anrdaemon at pubserver64:xterm:~ $ wbinfo -g | wc -l 20 anrdaemon at hosting64:xterm:~ $ wbinfo -g | wc -l 18 anrdaemon at daemon1:screen&0:~ $ wbinfo -u | wc -l 12 anrdaemon at hosting64:xterm:~ $ wbinfo -u | wc -l 11 Domain authorization works? not. anrdaemon at hosting64:xterm:~ $ sudo -iH [sudo] password for anr...

...t; domain computers:x:10003: domain sudoers:x:10006: domain admins:x:10000: domain guests:x:10002: cloud admins:x:10010: domain users:x:10001: remote users:x:10009: cloud users:x:10008: git admins:x:10007: cvs:x:10005: Even wbinfo lists groups/users incorrectly on different machines. anrdaemon at pubserver64:xterm:~ $ wbinfo -g | wc -l 20 anrdaemon at hosting64:xterm:~ $ wbinfo -g | wc -l 18 anrdaemon at daemon1:screen&0:~ $ wbinfo -u | wc -l 12 anrdaemon at hosting64:xterm:~ $ wbinfo -u | wc -l 11 Domain authorization works? not. anrdaemon at hosting64:xterm:~ $ sudo -iH [sudo] password for anr...

...t; domain computers:x:10003: domain sudoers:x:10006: domain admins:x:10000: domain guests:x:10002: cloud admins:x:10010: domain users:x:10001: remote users:x:10009: cloud users:x:10008: git admins:x:10007: cvs:x:10005: Even wbinfo lists groups/users incorrectly on different machines. anrdaemon at pubserver64:xterm:~ $ wbinfo -g | wc -l 20 anrdaemon at hosting64:xterm:~ $ wbinfo -g | wc -l 18 anrdaemon at daemon1:screen&0:~ $ wbinfo -u | wc -l 12 anrdaemon at hosting64:xterm:~ $ wbinfo -u | wc -l 11 Domain authorization works? not. anrdaemon at hosting64:xterm:~ $ sudo -iH [sudo] password for anr...

...; cloud admins:x:10010: >>> domain users:x:10001: >>> remote users:x:10009: >>> cloud users:x:10008: >>> git admins:x:10007: >>> cvs:x:10005: >>>> Even wbinfo lists groups/users incorrectly on different machines. >>>> anrdaemon at pubserver64:xterm:~ >>> $ wbinfo -g | wc -l >>> 20 >>> anrdaemon at hosting64:xterm:~ >>> $ wbinfo -g | wc -l >>> 18 >>>> anrdaemon at daemon1:screen&0:~ >>> $ wbinfo -u | wc -l >>> 12 >>> anrdaemon at hosting64:xterm:~ &gt...

...>>> domain users:x:10001: >>>> remote users:x:10009: >>>> cloud users:x:10008: >>>> git admins:x:10007: >>>> cvs:x:10005: >>>>> Even wbinfo lists groups/users incorrectly on different machines. >>>>> anrdaemon at pubserver64:xterm:~ >>>> $ wbinfo -g | wc -l >>>> 20 >>>> anrdaemon at hosting64:xterm:~ >>>> $ wbinfo -g | wc -l >>>> 18 >>>>> anrdaemon at daemon1:screen&0:~ >>>> $ wbinfo -u | wc -l >>>> 12 >>>&gt...

...001: > >>>> remote users:x:10009: > >>>> cloud users:x:10008: > >>>> git admins:x:10007: > >>>> cvs:x:10005: > >>>>> Even wbinfo lists groups/users incorrectly on different > >>>>> machines. anrdaemon at pubserver64:xterm:~ > >>>> $ wbinfo -g | wc -l > >>>> 20 > >>>> anrdaemon at hosting64:xterm:~ > >>>> $ wbinfo -g | wc -l > >>>> 18 > >>>>> anrdaemon at daemon1:screen&0:~ > >>>> $ wbinfo -u | wc -l...