Dear All, I have the following problem with smbpasswd: I would like to use a real WinNT PDC for authentication purposes, and regitered the computer account in the PDC. When I trying to run smbpasswd -j DOMAINNAME, I get the folloing testlin:~ # smbpasswd -j DOMAINNAME modify_trust_password: machine xxx.xxx.xxx.xxx rejected the session setup. Error was : code 131. 1999/06/24 21:41:29 : change_trust_account_password: Failed to change password for domain DOMAINNAME. Unable to join domain DOMAINNAME. Can anybody help me, what is happening? Andrash Kovach
On Fri, 25 Jun 1999, Andrash Kovach wrote:
-> testlin:~ # smbpasswd -j DOMAINNAME
->
-> modify_trust_password: machine xxx.xxx.xxx.xxx rejected the session
-> setup. Error was : code 131.
-> 1999/06/24 21:41:29 : change_trust_account_password: Failed to change
-> password for domain DOMAINNAME.
-> Unable to join domain DOMAINNAME.
First, you must create a domain account using server manager on the domain
controller. Then make sure your smb.conf file is correct--it should be
set to security=domain, domain server=<insert domain controller here>, and
domain=DOMAINNAME. Now stop your SMB services and try smbpasswd again:
smbpasswd -j DOMAINNAME -r <insert domain controller here>
Hope that helps.
Kevin
---
|\ _,,,---,,_
ZZZzz /,`.-'`' -. ;-;;,_
|,4- ) )-,_. ,\ ( `'-' Kevin Alan Pieckiel
'---''(_/--' `-'_)
kapieckiel@harding.edu
(This message was written with vi)
Good luck finding an answer to this. I've been fighting with the same problem for over a week now and have posted to the list twice asking for help. I've gotten a couple suggestions, none of which has made any difference. I have the "teach yourself samba in 24 hours" and it hasn't helped either. I'm awaiting another samba book that I have on order in the hopes that it will provide a clue. If you do figure it out please let me know. Duane Andrash Kovach wrote:> > Dear All, > > I have the following problem with smbpasswd: > > I would like to use a real WinNT PDC for authentication purposes, and > regitered the computer account in the PDC. > When I trying to run smbpasswd -j DOMAINNAME, I get the folloing > > testlin:~ # smbpasswd -j DOMAINNAME > > modify_trust_password: machine xxx.xxx.xxx.xxx rejected the session > setup. Error was : code 131. > 1999/06/24 21:41:29 : change_trust_account_password: Failed to change > password for domain DOMAINNAME. > Unable to join domain DOMAINNAME. > > Can anybody help me, what is happening? > > Andrash Kovach
I've verified that smbpasswd is connecting to the correct ip yet it still cannot join the domain. I've tried everything I can think of plus several suggestions from others but it still will not work. Looks like I'm stuck with NT. Duane Rick Flower wrote:> > Andrash Kovach writes: > > Dear All, > > > > I have the following problem with smbpasswd: > > > > I would like to use a real WinNT PDC for authentication purposes, and > > regitered the computer account in the PDC. > > When I trying to run smbpasswd -j DOMAINNAME, I get the folloing > > > > testlin:~ # smbpasswd -j DOMAINNAME > > > > modify_trust_password: machine xxx.xxx.xxx.xxx rejected the session > > setup. Error was : code 131. > > 1999/06/24 21:41:29 : change_trust_account_password: Failed to change > > password for domain DOMAINNAME. > > Unable to join domain DOMAINNAME. > > I just ran into this this morning on one of our servers I upgraded and > after poking around a bit I found the answer. It turned out that we > had two machines with the same name, but in slightly different domains > (not NT domains, but internet domains). As it turned out, Samba was > trying to talk with the wrong machine which was probably another Sun > workstation instead of an NT PDC.. I put an entry into /etc/hosts that > had the correct IP address for the PDC (with the right name of course > -- and NOT fully-qualified) and then all was happy! > > So, to sum it up, double-check that you are communicating with the > correct PDC (read that was the correct IP address), since even the > smbpasswd command doesn't appear to honor the fully qualified domain > name of the PDC if it is specified on the command-line. > > If you wish, you can read that particular error "machine xxx rejected > the session setup. error was : code 131" as a standard "connection > refused" message that you might be more familiar with. (I'm not 100% > sure about this, but in my case that was what appeared to be the case) > > -- Rick