[cifs-protocol] RE: Specific sockaddr layout in MS-ADTS 7.3.1.7

2008-07-11 Thread Hongwei Sun
Hi, Andrew,

   We have completed our investigation on Window clients implementation 
regarding NETLOGON_NT_VERSION_5EX_WITH_IP bit.   We confirmed that in all 
clients of Windows NT 4 or higher,  NETLOGON_NT_VERSION_5EX_WITH_IP bit of 
NtVersion flag is always set for NetBIOS based mailslot ping,  but is never  
set for LDAP ping.   We verified in our testing that clients did set this bit 
when a NetBIOS domain name is used.

  Please let us know if you have further questions.

Thanks !

Hongwei


-Original Message-
From: Andrew Bartlett [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 5:21 PM
To: Hongwei Sun
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Specific sockaddr layout in MS-ADTS 7.3.1.7

On Thu, 2008-06-26 at 14:03 -0700, Hongwei Sun wrote:
 Hi, Andrew,



Thanks for your question regarding NETLOGON_NT_VERSION_5EX_WITH_IP
 flag.



In terms of the server, it is not deprecated.  That is, current
 servers still support requests that include this flag and respond
 appropriately.  For a server to be interoperable with Windows clients,
 it needs to accept the flag in either way whenever it is sent.  The
 documentation explains what server should do if the bit is set in the
 NtVersion flag and what server should do if it is not set and that it
 should be prepared to accept a communication that contains this flag
 at any time.  Any actions taken by a Windows client based on this flag
 do not affect the interoperability of a server implementation.

All those words, yet no new information!

Can you please answer the question:  What windows client will set this flag, 
and under what circumstances?  If no Microsoft clients set this flag, then can 
the documentation be updated to reflect this.

This is an important question for implementers.  We could spend all year 
implementing things that Microsoft servers do, but if we concentrate our 
efforts on the things that exist the the real world, then we are all much more 
productive.

Perhaps you could escalate this question to someone who is able to find this 
out?

Andrew Bartlett

--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team   http://samba.org
Samba Developer, Red Hat Inc.
___
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol


[cifs-protocol] RE: Specific sockaddr layout in MS-ADTS 7.3.1.7

2008-06-19 Thread Andrew Bartlett
On Thu, 2008-06-19 at 09:06 -0700, Hongwei Sun wrote:
 Andrew,
 
Which flag are you referring to ?  The only flag I know of related
 to this is the NETLOGON_NT_VERSION_5EX_WITH_IP flag which the client
 must specify for the server to fill in the DcSockAddr field.  Please
 confirm.

That's what I mean.  I note that modern clients such as Vista Ultimate
don't seem to send this flag in their default query, so wondered if this
part of the protocol was some deprecated experiment no longer in use.  

Alternately, in what situations would a Microsoft client set this flag?

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team   http://samba.org
Samba Developer, Red Hat Inc.


signature.asc
Description: This is a digitally signed message part
___
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol


[cifs-protocol] RE: Specific sockaddr layout in MS-ADTS 7.3.1.7

2008-06-17 Thread Andrew Bartlett
On Thu, 2008-06-12 at 11:39 -0700, Hongwei Sun wrote:
 Andrew,
 
   For your questions, the following are responses.
 
  1. when IPv6 is in use?
 
Our current server versions only support returning IPv4.  We can add the 
 information into the documentation.
 
  2. Are there any other protocols (hey IPX ;-) that are possibly represented 
 by this wire element?
 
No other protocols , IP only.

Is this a deprecated flag?  What clients send it?  Why do new clients
not send it?

Thanks,

Andrew Bartlett

-- 
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team   http://samba.org
Samba Developer, Red Hat Inc.  http://redhat.com



signature.asc
Description: This is a digitally signed message part
___
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol