Hi obaid,
So we are waiting for you to provide us the exact meaning of the
SupportedEncTypes in GetDomainInfo in Netlogon RPC.
Am I right ?
Regards.
Matthieu.
On 08/15/2009 02:38 AM, Obaid Farooqi wrote:
Hi Matthieu:
I did not run the test for win 7 and WS2008R2 but code in unchanged (at the
writing of this email) so I would expect the behavior to be same as vista and
ws2008.
Regards,
Obaid Farooqi
Sr. Support Escalation Engineer | Microsoft
-Original Message-
From: Matthieu Patou [mailto:mat+informatique.sa...@matws.net]
Sent: Friday, August 14, 2009 3:10 PM
To: Obaid Farooqi
Cc: p...@tridgell.net; cifs-proto...@samba.org
Subject: Re: [cifs-protocol] Explain not standard behaviour of Windows 2003
server
On 08/14/2009 08:01 PM, Obaid Farooqi wrote:
Hi Matthieu:
Here is what I found out about SupportedEncTypes:
Client Server SupportedEncValue
-- -- -
WS2003 WS2008 0x
WS2008 WS2003 0x0
WS2008 WS2008 0x1f
Vista WS2008 0x1f
I'll let you know the modifications to MS-NRPC with respect to
SupportedEncTypes as soon as I have them.
I do not have the opportunity to do it test with windows 7 and windows
2008 R2 if you can investigate with this it could be great.
Matthieu.
Regards,
Obaid Farooqi
Sr. Support Escalation Engineer | Microsoft
-Original Message-
From: Matthieu Patou [mailto:mat+informatique.sa...@matws.net]
Sent: Thursday, August 13, 2009 10:58 AM
To: Obaid Farooqi
Cc: p...@tridgell.net; cifs-proto...@samba.org
Subject: Re: [cifs-protocol] Explain not standard behaviour of Windows 2003
server
Hi Obaid,
Find attach 2 extraction of DCERPC:
* dcerpc_w2k3 with a w2k3 DC and a w2k8 client,
* dcerpc_w2k8 with a w2k8 DC and a w2k3 client
I added an byte extraction of the GetDomainInfo reply for both. In w2k3
exchange the frame 14 is the first GetDomainInfo reply, in w2K8 it's frame 31.
Regards.
Matthieu.
On 08/11/2009 08:23 PM, Obaid Farooqi wrote:
Hi Matthieu:
Thanks for the info. One more request, please send me the traces that you
collected. As you mentioned, I'll not be able to decrypt the messages but it
will still be useful to see what messages are passing. Please also mention in
what frames you saw the issue.
Regards,
Obaid Farooqi
Sr. Support Escalation Engineer | Microsoft
-Original Message-
From: Matthieu Patou [mailto:m...@matws.net]
Sent: Tuesday, August 11, 2009 12:23 AM
To: Obaid Farooqi
Cc: p...@tridgell.net; cifs-proto...@samba.org
Subject: Re: [cifs-protocol] Explain not standard behaviour of Windows
2003 server
Hello Obaid,
So I did the following tests:
W2K8 "client" with a W2K3R2 server
W2K8 "client" with a W2K8 server
All computers are setuped without any special things: I installed
windows 2003/2008 and the run a dcpromo for the dc, and then make the
"client" join the AD domain.
For the w2K3R2 server the ad level is 2000, and for w2K8 the ad level
is 2008.
I did the trace when I faced bugs with samba4 with W2K8 as a SMB
client or server, so this trace were done in order to see what's the
difference between windows 2003/2008 as a DC and samba4.
Note that I noticed the same behavior when looking at trace of other
samba team member.
Let me know if you do not see the same problem.
Matthieu.
On 08/11/2009 02:42 AM, Obaid Farooqi wrote:
Hi Matthieu:
Let's tackle it from a different angle. If you tell me your
configuration/environment and what you are exactly doing, I may be able to
reproduce this and debug Windows to see what is happening.
Please let me know details of your environment and you what are you testing.
Regards,
Obaid Farooqi
Sr. Support Escalation Engineer | Microsoft
-Original Message-
From: Matthieu Patou [mailto:m...@matws.net]
Sent: Monday, August 10, 2009 1:02 PM
To: Obaid Farooqi
Cc: p...@tridgell.net; cifs-proto...@samba.org
Subject: Re: Explain not standard behaviour of Windows 2003 server
Hi Obaid,
The frames are encrypted (schannel encryption).
Do you have the opportunity to rebuild a wireshark if so using my
patchs you can quite easily decrypt them of not then it's gonna be
more difficult ...
Matthieu.
On 08/10/2009 08:47 PM, Obaid Farooqi wrote:
Hi Matthieu:
Please send me the network traces for both Windows 2003 and Windows 2008.
Please also mention the number of frames that have the problem. Please also
include the information about the environment, especially client OS (DC OS is
obvious from question).
Regards,
Obaid Farooqi
Sr. Support Escalation Engineer | Microsoft
-Original Message-
From: Matthieu Patou [mailto:m...@matws.net]
Sent: Saturday, August 08, 2009 1:55 PM
To: p...@tridgell.net; Interoperability Documentation Help;
cifs-proto...@samba.org
Subject: Explain not standard behaviour of Windows 2003 server
Hello,
In MS-NRPC for response to GetDomainInfo the DC usually return a
NETLOGON_DOMAIN_INFO structure.
This stucture as explained in 2.2.
