Hi,
after a few days I found the solution. The problem was in bad SID
numbers.
The Machine Account in the /etc/smbpasswd
vs3$:501:F74786067472.3E527018D189760:382721F51C7C.C9C1E9A81BB
145:[W ]:LCT-416E659B:
has to be transformed into LDAP directory with the same number:
Change the add machine script to this:
add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M
%u
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Santos Soler
MCP, Network+, A+
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
To unsubscribe from this list go to the following URL and read the
Roberto Mason wrote:
I've added the seal registry patch and modified the script to include add
machine script. I also added root to the smbpasswd and enabled the user,
and still I get unknown user or password. There's something still missing.
I seem to remember having this same problem and solving
Roberto Mason wrote:
I've added the seal registry patch and modified the script to include add
machine script. I also added root to the smbpasswd and enabled the
user,
and still I get unknown user or password. There's something still missing.
I seem to remember having this same problem and
you were so close. It's a combination of the two.
/usr/local/bin/smbldap-useradd.pl -a -w computerName
from smb.conf
add machine script = /usr/local/bin/smbldap-useradd.pl -a -w %m
-=Carl=-
J B Bell [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
--
To unsubscribe from this list
may want to check if this is uncommented in your smbldap-useradd.pl file
if (!$with_smbpasswd) {
# (jtournier)
# Objectclass sambaSAMAccount is now added directly by samba when joigning
the domain (for samba3)
if (!add_samba_machine_mkntpwd($userName, $userUidNumber)) {
die $0: error while
On Wed, 2003-10-15 at 17:11, Carl Weiss wrote:
may want to check if this is uncommented in your smbldap-useradd.pl file
if (!$with_smbpasswd) {
# (jtournier)
# Objectclass sambaSAMAccount is now added directly by samba when joigning
the domain (for samba3)
if
After verifying my smb.conf file, the only thing that changed was this
panic action command was added. My smb.conf is attached.
All our workstations stopped working. If I change the computer name,
switch to workgroup, then try to re-join the domain under a different
computer name, it works. Do
Irving,
On Tue, Dec 03, 2002 at 05:26:42PM -0500, Irving Carrion wrote:
After verifying my smb.conf file, the only thing that changed was this
panic action command was added. My smb.conf is attached.
All our workstations stopped working. If I change the computer name,
switch to workgroup,
Well that's because I started out using the following:
passdb backend = tdbsam:/etc/samba/passdb.tdb unixsam
Through debugging and trial and error I ended up with the smb.conf I
sent you. The only reason I'm using smbpasswd format now is because I
can verify that all machine accounts are listed.
On Tue, Dec 03, 2002 at 05:41:05PM -0500, Irving Carrion wrote:
Well that's because I started out using the following:
passdb backend = tdbsam:/etc/samba/passdb.tdb unixsam
Well, shoot -- that was my best guess. :)
All our workstations stopped working. If I change the computer name,
switch
11 matches
Mail list logo
