[cifs-protocol] Incoherent values in MS-FRS1.pdf in comparison to traces
hongweis at microsoft.com
Wed Aug 24 12:43:26 MDT 2011
Thanks for your question. We will work on it and respond to you soon.
From: cifs-protocol-bounces at cifs.org [mailto:cifs-protocol-bounces at cifs.org] On Behalf Of Matthieu Patou
Sent: Wednesday, August 24, 2011 11:35 AM
To: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: [cifs-protocol] Incoherent values in MS-FRS1.pdf in comparison to traces
Hello Dochelp team,
Paragraph 22.214.171.124.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 ?
Samba Team http://samba.org
Private repo http://git.samba.org/?p=mat/samba.git;a=summary
More information about the cifs-protocol