[Samba] samba migration woes
myitguru at yahoo.com
Wed Sep 17 07:32:14 GMT 2008
Thank you for the response Helmut,
The problem when I do that is the Centos box with Samba 3.0.28 generates
an schannel_store.tdb in the "private" dir when I attempt to login from a
client machine. It allows the login but denies access to the users home
dir on the samba server. In the schannel_store.tdb some machine info is
placed similar to what you see in the secrets.tdb file. This causes problems
with the client machines not being able to find the user profile...etc. I would
like to fix this issue the "right way" whatever that is, instead of starting over
and rejoining all the machines in the domain again. Any insights would be
----- Original Message ----
From: Helmut Hullen <Hullen at t-online.de>
To: samba at lists.samba.org
Sent: Monday, September 15, 2008 11:51:00 PM
Subject: Re: [Samba] samba migration woes
Du (myitguru) meintest am 15.09.08:
> I am trying to migrate samba from a box with Mandrake 10.1 with Samba
> 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two
> versions of samba are too differnet to simply copy the config and tdb
> files over to the new box and the Mandrake box won't upgrade past
> 3.0.10. I could really use some suggestions. Thanks
Where's the problem?
If you take the old "samba.cnf" for the new samba version then samba
will tell you which parameters are not allowed ("obsolete").
testparm -s >/dev/null
If your passwd file lies in "/etc/samba/private" then you have to copy
the complete directory contents to the new machine (especially a file
"secrets.tdb" with the "local SID").
You don't need to copy the tdb files in "/var/lock/samba" - they are
created new if they don't exist on the new system.
Perhaps you need to put every client out of the domain, restart the
client and put it into the domain again.
To unsubscribe from this list go to the following URL and read the
More information about the samba