> /sbin/e-smith/db accounts set $machineName$ machine > /usr/sbin/useradd -c "Hostname account for $machineName$" - > d /noexistingpath -s /bin/false $machineName$ > /usr/bin/passwd -l $machineName$ > /usr/bin/smbpasswd -a -m $machineName$ Yes, I understood this from the beginning. Actually, it is not necessary for the machine-create-account script to perform the smbpasswd -a -m function as this is done by samba after a machine account is successfully created in the passwd database. The only time you would need to perform this task manually is when you want to add another samba machine to the domain. This can be seen in the fact that 99% of Samba servers simply use only the /usr/sbin/useradd applet in the add user script line and the fact that the rewrite of the machine-create-account script that I sent doesn't do this..
Fact is, the above confuses Samba. Or maybe more accurately, it causes Samba to spit out some really strange log entries when you run the log level to 10. I don't think the issue as detailed in the experinced users forum is unique as I was able to reproduce it not out of happenstance but by doing what the user in the forum did. Granted, most people aren't seeing this, but from a developers standpoint it raises a red flag when you can reproduce an issue that someone else finds. I'm wondering if many people have even tried doing this??? After reading your comments last night, I went back in and reinstalled Samba and your fragments and successfully joinned a brand new Win2k laptop to the domain (really disappointed me actually... after spending a several hours working on a fix for a fragment that I thought was busted). But, when I removed this new laptop from the domain and tried to rejoin it again under the same netbios name, bang there was the error message (yes, I did pull out all user account dbase entries that the four functions your provided removes). >> AFAIK there is no 'samba' way to remove a machine from a domain once it > is added. You can remove the machine by doing the reverse to the above > directly via the command-line: For now this is true. My understanding is that they are working on a way to automate the process. Best regards, Greg J. Zartman -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
