search for: 3000046

.... Wed Apr 22 12:04:08 2020 21715 0 DENY_ALL 0x100080 RDONLY NONE /mnt/data-old/oldshare . Thu Apr 23 09:23:14 2020 21715 3000036 DENY_NONE 0x80 RDONLY NONE /mnt/data-old/oldshare . Thu Apr 23 08:19:59 2020 21707 3000046 DENY_NONE 0x80 RDONLY NONE /mnt/data-old/oldshare . Thu Apr 23 08:18:38 2020 21511 3000047 DENY_NONE 0x80 RDONLY NONE /mnt/data-old/oldshare . Thu Apr 23 07:08:11 2020 20398 3000047 DENY_NONE 0x80 RDONLY NONE...

...nistrator:*:3000036:3000037::/home/SANDBOX/administrator:/bin/false SANDBOX\guest:*:3000043:3000037::/home/SANDBOX/guest:/bin/false SANDBOX\defaultaccount:*:3000044:3000037::/home/SANDBOX/defaultaccount:/bin/false SANDBOX\krbtgt:*:3000045:3000037::/home/SANDBOX/krbtgt:/bin/false SANDBOX\wintahder:*:3000046:3000037::/home/SANDBOX/wintahder:/bin/false SANDBOX\joindomain:*:3000066:3000037::/home/SANDBOX/joindomain:/bin/false using wbinfo -u but no SANBOX users displayed. LUMAD\joindomain LUMAD\mdummy LUMAD\tdummy Based on my observation the idmap range of SANDBOX is different from the Windows Server...

...NFO\domain guests:x:3000013: WNETINFO\domain computers:x:3000043: WNETINFO\domain controllers:x:3000044: WNETINFO\schema admins:x:3000006: WNETINFO\enterprise admins:x:3000007: WNETINFO\group policy creator owners:x:3000008: WNETINFO\read-only domain controllers:x:3000045: WNETINFO\dnsupdateproxy:x:3000046: WNETINFO\ti:x:3000047: wnetin:~ # wnetin:~ # getent passwd | grep WNETINFO WNETINFO\administrator:*:0:100::/home/administrator:/bin/bash WNETINFO\guest:*:3000012:100::/home/guest:/bin/bash WNETINFO\krbtgt:*:3000018:100::/home/krbtgt:/bin/bash WNETINFO\user:*:3000021:100::/home/user:/bin/bash wne...

..._UID xidNumber: 0 distinguishedName: CN=S-1-5-21-1768301897-3342589593-1064908849-500 dn: CN=S-1-5-21-1768301897-3342589593-1064908849-2101 cn: S-1-5-21-1768301897-3342589593-1064908849-2101 objectClass: sidMap objectSid: S-1-5-21-1768301897-3342589593-1064908849-2101 type: ID_TYPE_BOTH xidNumber: 3000046 distinguishedName: CN=S-1-5-21-1768301897-3342589593-1064908849-2101 Check for duplicate 'xidNumbers' Also, as you say the other DC died (or is that fried ?), check the FSMO roles and ensure there is no mention of the dead DC in sam.ldb (you may have to use '--cross-ncs' & -sho...

Rowland, no domain user can authenticate on any system and running sysvolreset followed by sysvolcheck results in a crash. If the sysvol permissions are correct, sysvolcheck does not crash. If I attempt to join a NAS or workstation to the domain I get NT_STATUS_INVALID_SID. Researching these symptoms turns up a thread about a corrupt idmap.ldb where a group SID and user SID may be the same or

...: CN=S-1-5-21-1768301897-3342589593-1064908849-500 > > dn: CN=S-1-5-21-1768301897-3342589593-1064908849-2101 > cn: S-1-5-21-1768301897-3342589593-1064908849-2101 > objectClass: sidMap > objectSid: S-1-5-21-1768301897-3342589593-1064908849-2101 > type: ID_TYPE_BOTH > xidNumber: 3000046 > distinguishedName: CN=S-1-5-21-1768301897-3342589593-1064908849-2101 > > Check for duplicate 'xidNumbers' > Also, as you say the other DC died (or is that fried ?), check the FSMO > roles and ensure there is no mention of the dead DC in sam.ldb (you may > have to use ...

...ompatible access:x:3000016: BUILTIN\remote desktop users:x:3000041: BUILTIN\network configuration operators:x:3000042: BUILTIN\incoming forest trust builders:x:3000043: BUILTIN\performance monitor users:x:3000044: BUILTIN\performance log users:x:3000045: BUILTIN\windows authorization access group:x:3000046: BUILTIN\terminal server license servers:x:3000047: BUILTIN\distributed com users:x:3000048: BUILTIN\iis_iusrs:x:3000049: BUILTIN\cryptographic operators:x:3000050: BUILTIN\event log readers:x:3000051: BUILTIN\certificate service dcom access:x:3000052: SAMDOM\cert publishers:x:3000053: SAMDOM \ras...

...: CN=S-1-5-21-1768301897-3342589593-1064908849-500 > > dn: CN=S-1-5-21-1768301897-3342589593-1064908849-2101 > cn: S-1-5-21-1768301897-3342589593-1064908849-2101 > objectClass: sidMap > objectSid: S-1-5-21-1768301897-3342589593-1064908849-2101 > type: ID_TYPE_BOTH > xidNumber: 3000046 > distinguishedName: CN=S-1-5-21-1768301897-3342589593-1064908849-2101 > > Check for duplicate 'xidNumbers' > Also, as you say the other DC died (or is that fried ?), check the FSMO > roles and ensure there is no mention of the dead DC in sam.ldb (you may > have to use ...