[cifs-protocol] Incoherent values in MS-FRS1.pdf in comparison to traces

[Obaid Farooqi]

Hi Matthieu:
Absolutely! Please feel free to contact us if you feel like it was not resolved.
Thank you for quick reply.

Regards,
Obaid Farooqi
Escalation Engineer | Microsoft

Exceeding your expectations is my highest priority.  If you would like to provide feedback on your case you may contact my manager at allisong at microsoft.com


-----Original Message-----
From: Matthieu Patou [mailto:mat at samba.org] 
Sent: Monday, August 29, 2011 10:54 AM
To: Obaid Farooqi
Cc: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: Re: Incoherent values in MS-FRS1.pdf in comparison to traces

Hi Obaid,

It seems so but I didn't reached the point where I was able to check it with requested done by samba4.
If it turns to be not 100% resolved I guess we can reopen this case or create a new one right ?

Matthieu.
On 29/08/2011 17:49, Obaid Farooqi wrote:
> Hi Matthieu:
>  From your reply, I can guess this issue is resolved now but I am not sure. Please conform if this issue is resolved or not.
>
> Regards,
> Obaid Farooqi
> Escalation Engineer | Microsoft
>
> Exceeding your expectations is my highest priority.  If you would like 
> to provide feedback on your case you may contact my manager at 
> allisong at microsoft.com
>
>
> -----Original Message-----
> From: Matthieu Patou [mailto:mat at samba.org]
> Sent: Friday, August 26, 2011 10:39 AM
> To: mat at samba.org
> Cc: Interoperability Documentation Help; pfif at tridgell.net; 
> cifs-protocol at samba.org
> Subject: Re: Incoherent values in MS-FRS1.pdf in comparison to traces
>
> I guess here I've been caught by the presentation of the documentation, when command X says what you should expect in command Y (on reply to command X).
>
>
> Matthieu.
>
> On 24/08/2011 18:35, Matthieu Patou wrote:
>> Hello Dochelp team,
>>
>>
>> Paragraph 3.3.4.4.3  COMM_COMMAND Is CMD_START_JOIN says:
>>
>> "COMM_VVECTOR is the local member version vector. If the local member 
>> knows m originators in its version vector, there MUST be m 
>> COMM_VVECTOR elements in the packet, one for each originator.
>> COMM_JOIN_TIME MUST be the current time."
>>
>> Traces between Window servers show no COMM_VVECTOR packet and no 
>> COMM_JOIN_TIME (for a SYSVOL replication), you can see it in the 
>> trace http://imaps.matws.net/mat/misc/joinfrs.gz  at packet 4643. To 
>> decode it you'll also need the attached keytab. It's worth noting 
>> that example on page 138 didn't show this packets as well.
>>
>>
>> Note in order to see the FRS packet you'll need a pretty recent 
>> version of wireshark as I did the dissector for it not so long ago, 
>> you can get a nightly build of wireshark at 
>> http://www.wireshark.org/download/automated/win32/ and you need a 
>> version with a SVN revision>  38476.
>>
>> Can you explain ?
>>
>>
>> Matthieu.
>>
>
> --
> Matthieu Patou
> Samba Team        http://samba.org
> Private repo      http://git.samba.org/?p=mat/samba.git;a=summary
>
>
>


--
Matthieu Patou
Samba Team        http://samba.org
Private repo      http://git.samba.org/?p=mat/samba.git;a=summary