Wireshark · Smb2-protocol: Re: [Smb2-protocol] SMB2 named pipes and TID

[tridge@xxxxxxxxx]

Ronnie,

 > I have one trace that contains an instance of DCERPC over a named pipe  and
 > where the pipe is slightly busy  so it returns a
 > STATUS_PENDING   followed slightly later by the real reply.

yep, I hit that too while running the Samba4 DCERPC tests on smb2. I
have this code in smb2_transport_finish_recv() to cope with it:

	if (NT_STATUS_EQUAL(req->status, STATUS_PENDING)) {
		/* the server has helpfully told us that this request is still being
		   processed. how useful :) */
		talloc_free(buffer);
		return NT_STATUS_OK;
	}

 > The weird thing here  and which breaks ethereal is that in both replies
 > the TID is suddenly 0   instead of the real value used in the request.

I hadn't noticed that! The Samba4 client lib doesn't check the tid in
the reply, so this didn't trip us up.

 > Apart from this   the client still seems happy   so it seems it does not
 > check the TID   or require it being the same in a reply as in the request

luckily we did the same thing :-)

Cheers, Tridge