Hello people! I have observed the following behavior when re-joining NT domains from Linux boxes (RH 5.2, fwiw). 1. follow the directions in the DOMAIN_MEMBER.txt (thanks Jeremy!) to successfully join a domain. 2. restart smbd and nmbd 3. log on to the domain, make use of all of the nice stuff. 4. reboot the Linux box 5. upon attempting to rejoin the domain I observe the following error message: [root@entropy /etc]# smbpasswd -j MEL -r sarett cli_net_auth2: Error NT_STATUS_ACCESS_DENIED cli_nt_setup_creds: auth2 challenge failed modify_trust_password: unable to setup the PDC credentials to machine SARETT. Error was : NT_STATUS_ACCESS_DENIED. 1999/05/17 18:44:35 : change_trust_account_password: Failed to change password for domain MEL. Unable to join domain MEL. Note that the local host has an entry in the PDC: Participation in the Domain worked before rebooting! I have observed this behavior with four different Linux boxes. It *could* be that the number of clients allowed to connect to the server is exceeded, but I can't tell since my research advisor maintains the NT systems and guards the admin password well, and he doesn't care much if our Linux boxes play in the Domain. thanks for any help, Rich Molecular Engineering Laboratory Department of Chemistry and Biochemistry University of California, Santa Cruz
In article <Pine.LNX.3.96.990517184145.18724S-100000@entropy.ucsc.edu> you write:>3. log on to the domain, make use of all of the nice stuff. >4. reboot the Linux box 5. upon attempting to rejoin the domain I observe >the following error message: >[root@entropy /etc]# smbpasswd -j MEL -r sarett >cli_net_auth2: Error NT_STATUS_ACCESS_DENIEDThat's because you have ran smbpasswd a second time. When smbpasswd is run the first time, it creates a password file which will be re-used. (You don't have to rerun smbpasswd to rejoin the domain; once you join the domain you are a member of the domain.) If you run smbpasswd a second time, it will delete the password file and you are hosed. From my experience smbpasswd will now never work; no one will be able to access the Linux box even if it says it joins the domain successfully. (If anyone knows why or knows how to get out of this mess, please drop me a note. Thanks in advance.) -- Ambrose C. Li / +1 416 321 0088 / Ming Pao Newspapers (Canada) Ltd. EDP department / All views expressed here are my own; they may or may not represent the views of my employer or my colleagues.
In article <19990520192035Z102406-7973+54@www.mingpaoxpress.com> I wrote:>If you run smbpasswd a second time, it will delete the password file >and you are hosed. From my experience smbpasswd will now never work; >no one will be able to access the Linux box even if it says it joins >the domain successfully. (If anyone knows why or knows how to get out >of this mess, please drop me a note. Thanks in advance.)Sorry to follow up on my own. I have now found out why samba doesn't work in my case. It's because I tried to run a samba binary, which is compiled on Linux 2.2, under Linux 2.0. After I recompiled samba on Linux 2.0, everything seems to work fine. -- Ambrose C. Li / +1 416 321 0088 / Ming Pao Newspapers (Canada) Ltd. EDP department / All views expressed here are my own; they may or may not represent the views of my employer or my colleagues.