[cifs-protocol] FW: Specific sockaddr layout in MS-ADTS 7.3.1.7
Hongwei Sun
hongweis at microsoft.com
Thu Jun 12 22:52:05 GMT 2008
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.
Thanks
----------------------------------------------------------
Hongwei Sun - Support Escalation Engineer
DSC Protocol Team, Microsoft
hongweis at microsoft.com
Tel: 469-7757027 x 57027
-----------------------------------------------------------
-----Original Message-----
From: Andrew Bartlett [mailto:abartlet at samba.org]
Sent: Thursday, June 05, 2008 5:42 PM
To: Hongwei Sun
Cc: cifs-protocol at cifs.org; pfif at tridgell.net
Subject: Re: Specific sockaddr layout in MS-ADTS 7.3.1.7
On Thu, 2008-06-05 at 09:03 -0700, Hongwei Sun wrote:
> Hi, Andrew,
>
> In response to your question regarding DcSocketAddr structure in NETLOGON_SAM_LOGON_RESPONSE_EX , we confirmed that this structure has the following layout .
>
> Bytes Elements ByteOrder Notes
>
> 0-1 sin_family LittleEndian Value should always be AF_INET
> 2-3 sin_port LittleEndian Value should always be 0
> 4-7 sin_addr BigEndian IPV4 address
> 8-15 sin_zero Just padding 0s
>
> We will update the documentation [MS-ADTS] accordingly in the future release. Thanks again for helping us improve protocol documentation.
And when IPv6 is in use?
Are there any other protocols (hey IPX ;-) that are possibly represented by this wire element?
Andrew Bartlett
--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc.
More information about the cifs-protocol
mailing list