[KLUG Members] samba malfunctions

[Adam Tauno Williams]

>>account_policy.tdb  
>>group_mapping.tdb   
>>netlogon_unigrp.tdb
>>ntdrivers.tdb  
>>ntforms.tdb    
>>ntprinters.tdb      
>>registry.tdb  
>>secrets.tdb   
>>share_info.tdb
>>wins.tdb
>>There are some utilities included with Samba that do *NOT* build and
>>install by defauly but are handy -
>These are in tdb-tools*.deb, okay. I'll install 'em and take a look.
>>Files such as wins.tdb, ntforms, ntprinters, ntdrivers can be nuked.
>>Then just restart samba and you start with a fresh file.
>So what happens when the rest get nuked? I think I know.

If your using an LDAP SAM, not much.  Most of the "secret" information, domain 
membership cdredentials, etc... get stored there.  If your using the file for 
everything, wiping something like secrets can be bad.  Other like group mapping 
just cause it to rever to defaults,  which can be a pain if your haven' 
doucmented well.

>>>Now, that was interesting. Does my workgroup/domain, FIRST, have a
>>>SID?
>>Yes.
>>>And how do I check it?
>>[root@littleboy /root]# rpcclient -U adam -W backbone littleboy
>>Password: rpcclient $> lsaquery domain BACKBONE has sid
>>S-1-5-21-2037442776-3290224752-88127236
>I restored the *.tdb files from the previous install and it now works. I
>think some domain ID, such as an SID, is generated and cached there, and

Yes.

>woe unto thee who lose it. 

If you loose the domain SID, your goose is cooked.

>The strange thing was, you could log onto a
>machine only if you had logged on before the *.tdb foul-up. If you

You haven't disabled caching of profiles via poledit.

>hadn't, it rejected you. Also, this was causing the smbclient PC backups
>to fail. Glad I found it.