naughton@domino.danielwoodhead.com
2000-Dec-04 18:43 UTC
Lotus Notes, Oplocks, and Unexpected Network Error
We use Lotus notes with email files in mapped home directories on the samba server. (RH6.2, 2.0.7). I had seen some information on the list about NT TSE with the same problem associated to oplock break failures. I noticed that if I restart the samba server, every single notes client would have this "Unexpected Network Error" problem and you have to logoff and log back on. Killing and restarting the client didn't fix it. I don't do that anymore :) Now its more sporadic, but still irritating. Has anyone else seen this with Lotus Notes clients? Even if you haven't, Notes stores it's data in *.nsf files, would something like "veto oplock files = /*.nsf" accomplish the same thing as "oplocks False" without the performance hit for everything else on the server? Thanks Dan Naughton
reinout.wijnveen@philips.com
2000-Dec-05 07:48 UTC
Lotus Notes, Oplocks, and Unexpected Network Error
Hi, Notes seems to be 'allergic' for any kind of reconnection to a network share if it has any data files on that share. I don't believe it's just *.nsf files. With older versions such a reconnection happened after an oplock break failure, newer samba releases copy the behaviour of NT: ignore and continue. If you are on NT Terminal Server Edition please make sure that every user has it's own daemon (no users sharing a single daemon). That might be the reason that restarting the Notes Client does not help. In our case we also aplied the following to get rid of the remaing "Unexepected network errors": More information: technet Q233082 regedt32 open: HKEY_LOCAL_MACHINE\\SYSTEM\CurrentControlSet\Services\Rdr\Parameters add value: Value Name : MultipleUsersOnConnection Data Type : REG_DWORD Value : 0 - Regards, Reinout Wijnveen "All those who believe in psychokinesis raise my hand" ICT-N/Philips Semiconductors Nijmegen Address: AC 0.039, Gerstweg 2, 6534 AE Nijmegen naughton@domino.danielwoodhead.com@SMTP@lists.samba.org on 12/04/2000 07:48:48 PM Sent by: samba-admin@lists.samba.org To: samba@samba.org@SMTP cc: Subject: Lotus Notes, Oplocks, and Unexpected Network Error Classification: We use Lotus notes with email files in mapped home directories on the samba server. (RH6.2, 2.0.7). I had seen some information on the list about NT TSE with the same problem associated to oplock break failures. I noticed that if I restart the samba server, every single notes client would have this "Unexpected Network Error" problem and you have to logoff and log back on. Killing and restarting the client didn't fix it. I don't do that anymore :) Now its more sporadic, but still irritating. Has anyone else seen this with Lotus Notes clients? Even if you haven't, Notes stores it's data in *.nsf files, would something like "veto oplock files = /*.nsf" accomplish the same thing as "oplocks False" without the performance hit for everything else on the server? Thanks Dan Naughton
> server. (RH6.2, 2.0.7). I had seen some information on the list about NT > TSE with the same problem associated to oplock break failures. I noticed > that if I restart the samba server, every single notes client would have > this "Unexpected Network Error" problem and you have to logoff > and log back > on. Killing and restarting the client didn't fix it. I don't do that > anymore :) Now its more sporadic, but still irritating. > > Has anyone else seen this with Lotus Notes clients?Not with Notes but: We have shares on Samba 2.0.6 kernel 2.2.14 (I guess - machine is not here at this location). There were some severe file access problems. It resulted in one destroyed file. I don't know if the DOS app behaves badly or the FS. I expect that later is not ! the case. The crash occured twice. Both times we had to roll back the system to a state several hours ago and switched back to the old NT server. Sadly to say but nobody of the specialists here - and anywhere else - could help me. The symptom could not be reproduced manually. Torture tests of the system house who built the DOS app are not available - so I had to dig in the dark. I read a lot about Samba and startet changing with oplock params. Now, for several days we have Samba running stabil with this odd app WITHOUT any trouble. I changed the following params in general section of smb.conf: strict locking = yes oplocks = False oplock break wait time = 20 oplock contention limit = 4 I am still not 100% save that the peace hit us but hope in silent that I solved the problem. So maybe you want to test this with your Notes environment, too. If anyone out there, with better knowledge of the oplock params, could teach me the most conservative settings of Samba or if my settings will really prevent overlapping writes I personally would highly appreciate to know this. (I will sleep better, though ;-) Robert Schott roottec.com ----------------------------------------------- security is an illusion (Bombolo)