On Wed, 2003-05-21 at 23:44, Glenn Sieb wrote:> We just went through a massive renumber, and cleanup of some services.
>
> I went to rejoin our main Samba server to the domain and I get: error
> setting trust account password: NT_STATUS_NO_USER_SESSION_KEY
>
> I've deleted the machine account on the domain, I've double checked
the
> smb.conf to make sure I have the right domain controller set, and I'm
> issuing: smbpasswd -j CORP -r DOMAINMACHINE -U CORP\+Administrator
>
> I have done this on another machine already--it worked fine (same command
> line)....
>
> It's Samba 2.2.8a (on both machines).. :-/
This occurs partly because Samba 2.2 does not have any real support for
session keys - it just 'knows' to use a couple of them in a few places.
Samba 3.0 has code to correctly pass these around, and to calculate them
for the various logon types. In Samba 3.0, we would particularly get
this error message when contacting DCs using NTLMv2, when we didn't have
that code right.
That all said, I'm quite surprised to see this in Samba 2.2 - I didn't
think it did anything sufficiently fancy cause this kind of error.
I'm interested as to how you got this message in an NTLM environment - I
would like to get on top of this behavior...
Andrew Bartlett
--
Andrew Bartlett abartlet@pcug.org.au
Manager, Authentication Subsystems, Samba Team abartlet@samba.org
Student Network Administrator, Hawker College abartlet@hawkerc.net
http://samba.org http://build.samba.org http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.samba.org/archive/samba/attachments/20030521/6db9b6ad/attachment.bin