[Samba] server change

[Bill Szkotnicki]

Is there one particular .tdb file that is used for authentication?
The new server has been running now for two weeks and I am thinking that 
I should be careful about replacing .tdb files.
It is only this one issue of workstations where we want more than one 
userid to logon that needs solving.

All of my .tdb files are here:

*New server:*
# ls -alrt
total 3396
drwxr-x---  2 root squid    4096 Jun 21 21:07 winbindd_privileged
-rw-r--r--  1 root root      696 Sep  4 15:12 gencache.tdb
drwxr-xr-x  2 root root     4096 Sep  4 15:12 perfmon
-rw-------  1 root root      696 Sep  4 15:12 ntforms.tdb
-rw-------  1 root root     4096 Sep  4 15:12 ntdrivers.tdb
-rw-------  1 root root     4096 Sep  4 15:12 group_mapping.tdb
drwxr-xr-x 14 root root     4096 Oct 24 13:16 ..
-rw-------  1 root root     4096 Oct 29 07:39 share_info.tdb
drwxr-xr-x  2 root root     4096 Nov 19 11:45 printing
-rw-------  1 root root    16384 Nov 28 11:47 registry.tdb
-rw-------  1 root root    12288 Nov 28 11:47 ntprinters.tdb
-rw-------  1 root root     4096 Nov 28 11:47 account_policy.tdb
-rw-r--r--  1 root root    72069 Nov 30 04:02 namelist.debug
-rw-r--r--  1 root root      220 Dec  1 09:44 browse.dat
-rw-r--r--  1 root root     4096 Dec  1 09:49 unexpected.tdb
-rw-r--r--  1 root root    61440 Dec  1 09:51 brlock.tdb
-rw-r--r--  1 root root   217088 Dec  1 09:51 sessionid.tdb
-rw-r--r--  1 root root    16893 Dec  1 09:52 wins.dat
-rw-------  1 root root    53248 Dec  1 09:52 wins.tdb
-rw-r--r--  1 root root     4096 Dec  1 09:52 notify.tdb
-rw-------  1 root root    57344 Dec  1 09:52 messages.tdb
-rw-r--r--  1 root root  2572288 Dec  1 09:52 locking.tdb
-rw-r--r--  1 root root   294912 Dec  1 09:52 connections.tdb
*Old server:*
ls -alrt
drwxr-xr-x 16 root root   4096 Nov  7  2006 ..
-rw-------  1 root root  16384 Dec 13  2006 registry.tdb
drwxr-xr-x  2 root root   4096 Dec 13  2006 perfmon
-rw-------  1 root root    696 Dec 13  2006 ntforms.tdb
-rw-------  1 root root   8192 Dec 13  2006 ntdrivers.tdb
-rw-------  1 root root   8192 Dec 13  2006 group_mapping.tdb
-rw-------  1 root root   8192 Dec 13  2006 account_policy.tdb
-rw-------  1 root root   8192 Dec 13  2006 share_info.tdb
-rw-r--r--  1 root root   8192 Jan 10  2007 gencache.tdb
drwxr-x---  2 root squid  4096 Jun  5  2007 winbindd_privileged
drwxr-xr-x  2 root root   4096 Mar  3  2008 printing
-rw-r--r--  1 root root  72686 Sep  7 04:14 namelist.debug
-rw-------  1 root root  16384 Sep 13 06:30 ntprinters.tdb
-rw-------  1 root root  40960 Nov 18 11:57 wins.tdb
-rw-r--r--  1 root root    696 Nov 18 11:57 sessionid.tdb
-rw-------  1 root root    696 Nov 18 11:57 messages.tdb
-rw-r--r--  1 root root    696 Nov 18 11:57 locking.tdb
-rw-r--r--  1 root root   8192 Nov 18 11:57 connections.tdb
-rw-r--r--  1 root root    696 Nov 18 11:57 brlock.tdb
-rw-r--r--  1 root root   8192 Nov 18 11:57 unexpected.tdb
-rw-r--r--  1 root root    286 Nov 18 12:44 browse.dat
-rw-r--r--  1 root root  13522 Nov 18 12:46 wins.dat







Andrew Richey wrote:
>
>
> Toby Bluhm wrote:
>> Bill Szkotnicki wrote:
>>> Hi,
>>> Recently we changed our samba server to a bigger and more powerful 
>>> system ( centos 5.2 )
>>> The config file and smbpasswd and other passwd and group files were 
>>> copied to the new server and it then assumed the same identity as 
>>> the old one in the dns and ip address.
>>> It seems to have gone very well except we now seem to have a problem.
>>> There are windows XP workstations that were domain joined to the old 
>>> server
>>> and now connect well to the new one.
>>> But if you try to login on one of these workstations with an ID that 
>>> was not logged onto it previously it does not authenticate.
>>> The solution is to unjoin and then rejoin the workstation but there 
>>> are a lot of them and we don't want to do that.
>>> Also it seems that this situation has arisen just recently and was 
>>> working before on the new server and so I am wondering what could 
>>> have happened earlier this week.
>>>
>>
>>
>> That info is held in the *.tdb files. Centos stores them in 
>> /var/cache/samba/. If the old & new server are both Centos, just copy 
>> them over from the old box. Stop samba first, make a backup copy - 
>> just in case, restart samba. The machines that you've rejoined to the 
>> new box will need to be rejoined again, but all others should be ok. 
>> The SID-to-UID mappings are in the tdb files too - it would probably 
>> be best to have all PCs reboot after the update - rejoin as needed.
>>
>> If the distros are different I think the tdb files are compatible, 
>> but I'm not sure.
>>
>
>
> On a related note... if you store your information via ldap (Samba 
> sids and such)... is it true you need not bother backing up or moving 
> any of the .tdb files?
>
> -Andrew