[Samba] Can not add a new NT Workstation to a new (vampired)
stephen at vermeulen.ca
Tue Dec 11 14:51:04 GMT 2007
Stephen Vermeulen wrote:
> I am replacing an old NT4.0 Server with a debian 4.0R1 etch Linux
> server (samba 3.0.24).
> This was with a completely fresh install of debian.
> My smb.conf is pretty simple:
> workgroup = BUTLER
> netbios name = STAR3
> passdb backend = tdbsam
> domain master = No
> domain logons = Yes
> os level = 33
> add user script = /usr/sbin/useradd -m '%u'
> delete user script = /usr/sbin/userdel -r '%u'
> add group script = /usr/sbin/groupadd '%g'
> delete group script = /usr/sbin/groupdel '%g'
> add user to group script = /usr/sbin/usermod -G '%g' '%u'
> add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null
> # wins server = [IP of wins server]
> comment = SAMBA File Server
> path = /home/files
> read only = No
> In addition I have the following smbusers file:
> star3:/etc/samba# cat smbusers
> root = Administrator
> testparm tells me this setup will give me a BDC.
> I first added the samba server (star3) to the old NT4 PDC using the
> server manager tool
> and then did a:
> net rpc join -S nova -UAdministrator%password
> This worked and I was able to access the machine from the PDC.
> I then did a vampire:
> net rpc vampire -S nova -W BUTLER -UAdministrator%password
> and this worked for most of the user accounts and machine accounts
> (there were some that
> had errors, but these were mostly for old users or machines that were
> long since gone), these
> errors look like:
What would be the best way (apart from reinstalling Linux) to clean up
between tests of this? Deleting all the *.tdb files? What about the
that the vampire produces? What about the unix groups it creates?
More information about the samba