extra trailing . on path for tree connect

[Sam Liddicott]

On 26/04/11 10:13, Sam Liddicott wrote:
>
> I'm getting some unexpected packet contents from a windows XP client 
> on restarting an interrupted samba 4 session.
>
> If I have an open windows explorer view on windows XP and then restart 
> Samba and then refresh the open window by executing from a command 
> window:
>
> start \\es3300-c5559f6a\test
>
> Then I get the unexpected packet below showing that an extra trailing 
> dot . is added to the path-name at offset 0x0094 so that the connect 
> attempt is to:
>
> \\es3300-c5559f6a\test.
>
> instead of
>
> \\es3300-c5559f6a\test
>
>
> 0000   00 00 00 01 00 06 00 17 c5 5c fe 34 00 00 08 00  .........\.4....
> 0010   45 00 00 8e 68 72 40 00 80 06 ae ea 0a 14 17 50 E...hr at ........P
> 0020   c0 a8 01 01 05 36 01 bd 36 66 3a d4 fc f3 74 55  .....6..6f:...tU
> 0030   50 18 fc c1 ec 97 00 00 00 00 00 62 ff 53 4d 42  P..........b.SMB
> 0040   75 00 00 00 00 18 07 c8 00 00 00 00 00 00 00 00  u...............
> 0050   00 00 00 00 00 00 ff fe 86 cb 00 c0 04 ff 00 62  ...............b
> 0060   00 08 00 01 00 37 00 00 5c 00 5c 00 45 00 53 00  .....7..\.\.E.S.
> 0070   33 00 33 00 30 00 30 00 2d 00 43 00 35 00 35 00  3.3.0.0.-.C.5.5.
> 0080   35 00 39 00 46 00 36 00 41 00 5c 00 54 00 45 00  5.9.F.6.A.\.T.E.
> 0090   53 00 54 00 *2e 00* 00 00 3f 3f 3f 3f 3f 00        
> S.T.*.*...?????.
>
> Does anyone recognize such behaviour, or know the cause of the . or 
> what it might signify? 

If I set up shares so that the trailing . represent a valid share, then 
windows also attempts a connection with a share whose name has the last 
character missing, e.g. \\es3300-c5559f6a\tes

So I begin to think that this is just the windows client "intelligently" 
responding to a situation when the session was reset and trying to see 
if the share was renamed or something. But there doesn't seem to be any 
special action required of the server.

Sam