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
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,
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 ca
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
Documentation Help; p...@tridgell.net;
cifs-proto...@samba.org
Subject: [cifs-protocol] Incoherent values in MS-FRS1.pdf in comparison to
traces
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
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
