Topic: What process creates a specific entry in /etc/samba/secrets.tdb?

[mdo]

A plea for help with a very unusual issue.

A server that we have upgraded from SME8 to SME9 (backup/restore of configuration and a process that we have used before) now seems to have broken Samba domain member relationship for the Windows desktop computers (all Win7). Users can logon with their last, cached profile as it looks like but a different user logon on these machines fails, also the logon as user "admin", the domain administrator.

Looking though the Samba side of things, I noticed with a closer look into Samba's "secrets.tdb" file that one entry that every other of our SME installations has (Samba always defined as [Windows] domain controller") is missing completely, a "SECRETS/DOMGUID" entry/record which should look similar to below (from a different server):

key(18) = "SECRETS/DOMGUID/HT"
data(16) = "\06b\5C\96\E21\96J\80l 3\F2U[w"

I use "tdbdump /etc/samba/secrets.tdb" as the way to examine the contents of that Samba ".tdb" file/database.

I need to find a way of either adding the missing entry (tdbtool insert KEY DATA seems to be a manual way) but I suspect that this might be too complicated (don't understand the data for this).

Where in the standard SME set up procedure will this be created? Do we need to change the domain name, then signal-event post-upgrade & reboot and then re-join all machines to the domain or is there an easier way?

Thanks, Michael

[janet]

mdo

A server that we have upgraded from SME8 to SME9 (backup/restore of configuration and a process that we have used before) now seems to have broken Samba domain member relationship for the Windows desktop computers (all Win7).

If that is the case, & you used the standard/default full backup & restore, then you should report a bug immediately.
Backup & restore should work seemlessly.

[mdo]

Yes you are right but I forgot to say that we investigated backups of older secrets.tdb files and found that entry missing already earlier so this was not a problem of the upgrade process. It seems that older versions of Samba could treat this differently? I do not believe that we are looking at a bug, I suspect that something happened to that server (most likely cause by user intervention) earlier already.

Thanks for your follow up.

Michael

[Stefano]

can you give us some details about the

backup/restore of configuration and a process that we have used before

part?

it would help us a lot to understand, 'cause, IIUC, you didn't use the standard "backup/restore" feature

thank you