Locking Worries

[Jeremy Allison]

"Romeril, Alan" wrote:
> 
> Hello All,
>         I`m wondering if there`s something wrong with the locking mechanism
> that shows itself when a Win2k client logs on and pulls a profile from a
> Samba server.  Having tried to plough through it, and ended up with a big
> headache, it`s time to bounce this off the Technical list.
>         Here`s the problem....
> A file, for example, ntuser.dat is opened by the client during a logon with
> an NTCreateX Request and an oplock is granted on the file in the NTCreateX
> Response.
> Later on in the logon the file is opened again by the client again with an
> NTCreateX Request which generates the following series from the Samba
> server.
>                 Packet                                          Time From
> NTCreateX Request
>         server -> Win2K client SMBlockingX Response
> 0.25ms
>         Win2K client -> server SMBlockingX Request
> 0.35ms
>         server -> Win2K client SMBlockingX Response
> 1.5ms
>         server -> Win2K client SMBntcreate Response
> 150ms   !!!
> 
> Compare that with Win2K logging on to NT4.
>                 Packet                                          Time From
> NTCreateX Request
>         NT server -> Win2K client SMBlockingX Response          0.8 ms
>         Win2K client -> NT server SMBlockingX Request                   2.7
> ms
>         NT server -> Win2K client SMBntcreate Response          0.5 ms

I need to see more details on the packets being sent here.
Can you either send a .cap file or tcpdump with the relevent
packets listed in accompanying text (to cut down on analysis
time) or send the contents of a debug level 10 log from the
Samba server please.

Jeremy.

-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------