search for: 11868bg

Displaying 7 results from an estimated 7 matches for "11868bg".

Did you mean: 1168b
2016 Oct 09
2
Problem with one User after upgrade to 4.5.0
...iscovered that one of my user accounts is completely borked. What is very strange is that everything in Samba looks okay. Here is the first problem symptom. The data is from the DC. total 80 drwxr-xr-x. 7 root root 4096 Oct 9 01:15 . drwx------+ 77 SAMDOM\prg-11868bg SAMDOM\domain users 20480 Oct 9 00:55 prg-11868bg drwx------+ 39 3001108 SAMDOM\domain users 4096 Oct 9 00:30 sln-11868bg Note that the directory sln-11868bg is owned by 3001108 instead of SAMDOM\sln-11868bg. But everything seems like it should be correct. For example: &g...
2016 Oct 09
0
Problem with one User after upgrade to 4.5.0
...counts is completely borked. What is very strange is that > everything in Samba looks okay. Here is the first problem symptom. > The data is from the DC. > > total 80 > drwxr-xr-x. 7 root root 4096 Oct 9 > 01:15 . > drwx------+ 77 SAMDOM\prg-11868bg SAMDOM\domain users 20480 Oct 9 > 00:55 prg-11868bg > drwx------+ 39 3001108 SAMDOM\domain users 4096 Oct 9 > 00:30 sln-11868bg > > Note that the directory sln-11868bg is owned by 3001108 instead of > SAMDOM\sln-11868bg. But everything seems like it should...
2016 Oct 10
2
Problem with one User after upgrade to 4.5.0
...n the new CentOS 7 box with a fresh install off sernet-samba 4.5.0 I get this incorrect result: > getent group ssh_users ssh_users:x:3001108: I went through every entry in the idmap.ldb and there are no duplicates. In fact the only place 3001108 shows up is as the uidNumber for account sln-11868bg which I showed earlier in the day: > getent passwd sln-11868bg sln-11868bg:*:3001108:3000513:John Q. Public:/home/sln-11868bg:/bin/bash Here is the idmap.txt. The SIDs are listed in first column, the description of the SID is in the second column, the xidNumber is in the third column and w...
2018 Apr 06
2
User idmap lost
...sh probably 10 times MYDOM\me:*:10000:10513::/home/me:/bin/bash MYDOM\mywife:*:10001:10513::/home/mywife:/bin/bash I then do: > cd /home > ls -altn drwx------+ 82   10000   10513 20480 Apr  5 23:36 me drwx------+ 43 3000112 3000513  4096 Apr  4 18:28 mywife >getent passwd MYHOME\prg-11868bg:*:10000:3000513:Paul R. Ganci:/home/prg-11868bg:/bin/bash MYHOME\sln-11868bg:*:3000112:3000513::/home/sln-11868bg:/bin/bash It seems after some small length of time the domain users group gidNumber reverts to its xidNumber as does my wife's uidNumber. I have no idea why this would occur and...
2018 Apr 06
2
User idmap lost
...he Bigger Boss uidNumber: 3001108 unixHomeDirectory: /home/mywife objectClass: top objectClass: posixAccount objectClass: person objectClass: organizationalPerson objectClass: user objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=mydom,DC=mydc,DC=co  m profilePath: \\mydom\home\Profiles\sln-11868bg pwdLastSet: 131111097150000000 msSFU30NisDomain: mydom msSFU30Name: mywife unixUserPassword: ABCD!efgh12345$67890 uid: mywife lastLogonTimestamp: 131672869851028400 whenChanged: 20180404034305.0Z uSNChanged: 7165 lastLogon: 131674502053144830 logonCount: 134145 distinguishedName: CN=My Wife,CN=User...
2016 Oct 09
4
Problem with one User after upgrade to 4.5.0
On 10/09/2016 02:51 AM, Rowland Penny via samba wrote: > Have you by any chance got another 3001108 'xidNumber' in idmap.ldb ? > If you give a user a 'uidNumber' attribute, the contents of this will be > used instead of the 'xidNumber' in idmap.ldb, hence you do not need to > (and probably shouldn't) use numbers in the '3000000' range. I managed to
2018 Apr 06
0
User idmap lost
...ectory: /home/mywife > objectClass: top > objectClass: posixAccount > objectClass: person > objectClass: organizationalPerson > objectClass: user > objectCategory: > CN=Person,CN=Schema,CN=Configuration,DC=mydom,DC=mydc,DC=co >  m > profilePath: \\mydom\home\Profiles\sln-11868bg > pwdLastSet: 131111097150000000 > msSFU30NisDomain: mydom > msSFU30Name: mywife > unixUserPassword: ABCD!efgh12345$67890 > uid: mywife > lastLogonTimestamp: 131672869851028400 > whenChanged: 20180404034305.0Z > uSNChanged: 7165 > lastLogon: 131674502053144830 > logonC...