I recently worked through a migration of an NT4 PDC to a Samba PDC using
the vampire command,
while doing this I ran into some problems, possibly including your problem.
There are at least two steps to this procedure that are not included in
most of the documentation
on how to do this that I
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:
[global]
workgroup = BUTLER
netbios name = STAR3
passdb backend = tdbsam
domain
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:
[global]
workgroup = BUTLER
netbios name = STAR3
passdb backend = tdbsam
domain
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:
[global]
workgroup = BUTLER
netbios name = STAR3
passdb backend = tdbsam
domain master = No
domain
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.
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
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.
...
I then decided to try adding a new Windows XP Pro workstation to the
domain (it had previously
been a member, but I had
