I have a Linux RedHat 7.2 system that I'm not able to get to rejoin our
domain which is using a Solaris 8 system running Samba 2.2.5 system as a
PDC. The Linux client is running Samba version 2.2.1a. I have tried with
and without a machine record in the smbpasswd file. I have tried various
arrangements of "smbpasswd -j domain -r system -Uadmin%passwd". The
error I get is not able to write to the passwd file. I do know that
Samba should not be running when you do this. Specific error message is:
Unable to write the machine account password for machine SEQUOIA in
domain RECOMMENDED.
I have other systems, Win2k, Solaris, and RedHat 7.2 that are working,
but I have not needed to try a rejoin to the domain with them.
--
Regards,
David Highley Phone: (206) 669-0081
Highley Recommended, Inc. FAX: (253) 838-8509
2927 SW 339th Street Email: dhighley@highley-recommended.com
Federal Way, WA 98023-7732 WEB: http://www.highley-recommended.com
With further testing and packet snarfing I find that the Linux client never sends any packets to the system it was directed to with the -r flag for the smbpasswd command. I have check ipchains and xinetd files and find nothing that should block this communication and in fact the system communicates fine except for this case of trying to join the domain. Now I'm really stumped. It is implying that it can not write the MACHINE.SID file which I believe should go into the /etc/samba directory which does exist. -- Regards, David Highley Phone: (206) 669-0081 Highley Recommended, Inc. FAX: (253) 838-8509 2927 SW 339th Street Email: dhighley@highley-recommended.com Federal Way, WA 98023-7732 WEB: http://www.highley-recommended.com
Well, I have fixed the join domain problem, but now I have many more questions. After using strace and log level of 10 I was still not able to pin down why it was having trouble writing files. So I took a guess and added an "smb passwd file" line in the smb.conf file. It was then able to create the secrets.tdb file and failed when it found no machine record in the smbpasswd file on our Solaris 8 Samba PDC system. I added a machine entry with the "smbpasswd -a -m sysname" command and now the system was able to join the domain. So the next step is a sanity check by starting the daemons and doing an "smbclient -L sysname" command, which promptly failed because it could not find an smbpasswd file on this client system. So why do we have the "password server = *" line to search for a server with the passwd information? So I have copied the smbpasswd file to all Samba systems so that they will function. This seems like an ugly solution. -- Regards, David Highley Phone: (206) 669-0081 Highley Recommended, Inc. FAX: (253) 838-8509 2927 SW 339th Street Email: dhighley@highley-recommended.com Federal Way, WA 98023-7732 WEB: http://www.highley-recommended.com