[cifs-protocol] Inability to use Win2k8 as a member server in Samba4 domain (was Clarify reserved bytes that are in fact used in LogonSamLogonEx response)
hongweis at microsoft.com
Wed Jul 29 19:04:38 MDT 2009
We created a new case to keep track of this issue. I will work with Nick on this issue. We just downloaded and rebuilt the latest tree and we should be able to run repro tomorrow morning.
I will keep you posted.
From: cifs-protocol-bounces at cifs.org [mailto:cifs-protocol-bounces at cifs.org] On Behalf Of Andrew Bartlett
Sent: Tuesday, July 28, 2009 8:04 PM
To: Sebastian Canevari
Cc: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: Re: [cifs-protocol] Inability to use Win2k8 as a member server in Samba4 domain (was Clarify reserved bytes that are in fact used in LogonSamLogonEx response)
On Tue, 2009-07-28 at 17:07 -0700, Sebastian Canevari wrote:
> Hi Andrew,
> I'm working with the product group in confirming my findings.
> I am pretty sure that the first two longs in array ExpansionRoom in
> NETLOGON_VALIDATION_SAM_INFO4 (22.214.171.124.13 MS-NRPC) are used for the
> LanmanSessionKey but like I said I need to confirm it with the product
> group before giving you a definitive answer.
Indeed. If I had looked more carefully at the Samba Team's netlogon IDL this would have been clear.
This means that the actual problem here is unrelated. Perhaps it needs a new case, but can you please reproduce the failure of Win2k8 to operate in a Samba4 domain, and see if you can tell us why this is the case. We have been unable to identify any other differences in the protocol stream at this time.
Authentication Developer, Samba Team http://samba.org
Samba Developer, Cisco Inc.
More information about the cifs-protocol