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
On Mon, 2007-12-10 at 07:17 -0700, Stephen Vermeulen wrote:
I was using the Administrator user name, and I was able to log into
the BUTLER domain on another Windows box as the Administrator and
access the file share on the samba box and create new files in the
folder
owned by Administrator.
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
