[PATCH] s3: Fix chained sesssetupAndX/tconn messages

Jeremy Allison jra at samba.org
Sat May 9 00:10:05 GMT 2009

On Wed, May 06, 2009 at 03:27:35PM -0700, Tim Prouty wrote:
> Volker (and any other chaining experts),
> In master a sesssetupAndX chained with a tconn will not correctly set
> the TID in the response header.  I'm seeing an XP client send this
> chained sesssetup/tconn when samba has security = share.  Samba's
> current behavior is to return a TID of 0 in the smb header rather than
> the actual TID.  This patch also updates the UID in the header as
> well.  I wanted to have someone who knows the chaining code well
> review this before I push it.

Pushed this as Volker already reviewed this and ok'ed it, and I
need this fix to make one of my home devices work :-).



More information about the samba-technical mailing list