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

Obaid Farooqi obaidf at microsoft.com
Wed Aug 24 13:26:33 MDT 2011

Hi Matthieu:
I'll help you with this issue and will be in touch as soon as I have an answer.

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: Wednesday, August 24, 2011 11:35 AM
To: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: Incoherent values in MS-FRS1.pdf in comparison to traces

Hello Dochelp team,


"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 Patou
Samba Team        http://samba.org
Private repo      http://git.samba.org/?p=mat/samba.git;a=summary

Microsoft is committed to protecting your privacy.  Please read the Microsoft Privacy Statement for more information.The above is an email for a support case from Microsoft Corp.REPLY ALL TO THIS MESSAGE or INCLUDE casemail at microsoft.com IN YOUR REPLY if you want your response added to the case automatically. For technical assistance, please include the Support Engineer on the TO: line. Thank you.

More information about the cifs-protocol mailing list