This may or not be related. We use a reasonable complex set of scripts that are contained along with KIX32.EXE and the .DLLs in the NETLOGON directory on several NT 4.0 DCs. Users complain that they have to log in more than once to get their drive mappings. These are mapped by one of the SCRs in the login sequence.
Examination with a Sniffer shows that the client attempts to lock KIX32.EXE after it has read the file. I believe that this is the action taken by SMB when trying to establish a Level II oplock. I can't see why the client would attempt to establish the lock after reading the file otherwise. At any rate, the server replies with an access violation errror and the script never executes.
I'd love to hear from anyone who has experienced this problem, particularly if you have a solution!!
Thanks
plane@yallournenergy.com.au