Changing WS password every new installation

[William Stuart]

The answer is yes.  The password is changed, if not instantly, then soon
after joining the domain.  This is not a SAMBA issue but part of the
protocol.

I work on an engineering network, and do not have admin privledges on the
domain, so I have to put in a request for a new trust account for
every installation or reinstallation of NT.

---
William Stuart  (william at hae.com)
"If Netscape is giving their software away, how do they make money?"
"Volume."

On Fri, 14 Aug 1998, Mike Klinkert wrote:

> Date: Fri, 14 Aug 1998 23:54:46 +1000
> From: Mike Klinkert <michael at cs.vu.nl>
> To: Multiple recipients of list <samba-ntdom at samba.anu.edu.au>
> Subject: Changing WS password every new installation
> 
> Hi all,
> 
> Let me start with boosting the ego of everyone involved with the development of
> Samba. Great work, thanx. 
> 
> Anyway, this is why I'm posting a message:
> The last few days I've been experimenting with the unattend installation method
> of NT (in this case the WS). Ergo, I try to make an installation with the right
> (OEM) drivers in place, etc and because of this I've to install NT many times.
> After the right network drivers were installed automatically, I noticed that NT
> could not login on the Samba domain (configured as a PDC). However, it did do
> that before my experiments. What I did was I set the password of the WS again
> by typing: "smbpasswd MACHINE$" and used "machine" as the password (my WS's
> name is not MACHINE ofcourse, it's just an example). This worked perfectly.
> However, I have to do this everytime before I install NT, or else joining the
> domain will fail (I noticed a "password fail" in the log.smb file, prefixed
> with a "Trust relationship" something).
> Am I missing something here? Is the password changed by the WS after the domain
> joining? Setting the password of the WS everytime you (re)install NT is
> somewhat annoying (especially if you forget to do it, since the unattend
> installation will fail. Well it doesn't exactly, it just needs user input, so 
> the installation is no longer unattended).
> 
> Mike Klinkert.
> 
>