I doff my hat, indeed, my SBS200 is running SP1.

(Microsoft never provided updates for SBS2000 beyond SP1,
there were individual updates for Windows, Exchange, SQL, IIE ... but they were partially incompatible with SBS2000, so there might be more machines out there!!)

I updated to SP4, now I get the next error: NT_STATUS_NOLOGON_WORKSTATION_TRUST_ACCOUNT

Is it possible, that this is already a known issue in Samba 3.2.0 and needs to be back-ported to Samba 3.0.30? See http://lists-archives.org/samba/34051-net-ads-join-fails-with-nt_status_nologon_workstation_trust_account.html

Kind regards and many thanks already!

Jens

P.S: Error details - configuration as before:

[2008/06/05 14:55:22, 3] libsmb/ntlmssp.c:ntlmssp_client_challenge(1018)
  Got challenge flags:
[2008/06/05 14:55:22, 3] libsmb/ntlmssp.c:debug_ntlmssp_flags(63)
  Got NTLMSSP neg_flags=0x60898215
[2008/06/05 14:55:22, 3] libsmb/ntlmssp.c:ntlmssp_client_challenge(1040)
  NTLMSSP: Set final flags:
[2008/06/05 14:55:22, 3] libsmb/ntlmssp.c:debug_ntlmssp_flags(63)
  Got NTLMSSP neg_flags=0x60088215
[2008/06/05 14:55:22, 3] libsmb/ntlmssp_sign.c:ntlmssp_sign_init(338)
  NTLMSSP Sign/Seal - Initialising with flags:
[2008/06/05 14:55:22, 3] libsmb/ntlmssp.c:debug_ntlmssp_flags(63)
  Got NTLMSSP neg_flags=0x60088215
[2008/06/05 14:55:22, 3] libsmb/cliconnect.c:cli_session_setup(1014)
  SPNEGO login failed: No logon workstation trust account
[2008/06/05 14:55:22, 1] libsmb/cliconnect.c:cli_full_connection(1658)
  failed session setup with NT_STATUS_NOLOGON_WORKSTATION_TRUST_ACCOUNT
Could not connect to server sbs2000.candeo.test
Connection failed: NT_STATUS_NOLOGON_WORKSTATION_TRUST_ACCOUNT
Failed to verify membership in domain!
[2008/06/05 14:55:22, 2] utils/net.c:main(1066)
  return code = -1


Guenther Deschner wrote:
Guenther Deschner wrote:
Jens Nissen wrote:
After migrating from 3.0.26a to 3.0.30 I cannot join my AD member server to the domain anymore:
I get a DCERPC_FAULT_INVALID_TAG.
As I didn't change my Windows 2000 SBS Server, this looks like a new feature in Samba 3.0.30.

You're probably not running the latest SP on the SBS server. I could only reproduce your problem with Windows 2000 GA version (no SPs installed at all). We'll add fallback code for the next release, but you should really consider upgrading to the lastest SP.

Ok, In v3-0-test I added code that should resolve your issue. Will be in the next 3.0 release (out really soon).

Guenther



--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to