On Saturday 02 March 2002 6:46 pm, Michael Brown wrote:
What do the Samba logs say? You can find them in somewhere like /var/log/samba, and the log level will be determined by the smb.conf parameter "log level" or "debug level".
We've tweaked the logging level upwards and when a machine fails to login, we get this in the logfile: ************* [2002/03/04 08:15:50, 1] smbd/service.c:make_connection(610) langlab_02 (10.13.2.52) connect to service Profiles$ as user guest (uid=503, gid=101) (pid 18176) [2002/03/04 08:16:32, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 18173 on port 34884 for dev = 900, inode = 104334 for dev = 900, inode = 104334, tv_sec = 3c832d3c, tv_usec = 9ac64 [2002/03/04 08:16:32, 0] smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock left by process 18173 after break ! For file pupils/SendTo/My Briefcase.lnk, dev = 900, inode = 104334. Deleting it to continue... [2002/03/04 08:16:32, 0] lib/util.c:smb_panic(1055) PANIC: open_mode_check: Existant process 18173 left active oplock. ************* I've disabled oplocks on all shares and the problem seems to have gone away. I still don't understand why this problem occured, and was only present on the W2K clients. I suspect that for performance reasons we ought to have oplocks enabled on the home directory shares, but clearly, reliability is more important than performance. Cheers -- Phil Driscoll