[KLUG Members] Re:Samba reprocess config file question

[Bob Kanaley]

> Date: Wed,  6 Mar 2002 14:26:32 -0500
> From: adam@morrison-ind.com
> To: members@kalamazoolinux.org
> Subject: Re: [KLUG Members] Samba reprocess config file questions
> Reply-To: members@kalamazoolinux.org

> >I have not been able to prevent a Win98 0E exception error that occurs
when
> >certain Win98 clients accesses some specific Samba shares on my cenral
file
> >server. The error is reproducible and leads to a Win98 lockup some time
> >after the blue screen, generally resulting in loss of data.

>
> I've never seen that one,  but I've seen some strange things.  I'd suspect
> oplocks,  which are a bit wobbly in old versions of Samba.  Can't hurt to
try
> and turn them off.


Until I can figure out how to migrate my users to the new Monarch server
running on RedHat 7.2, my Samba server is Samba 1.9.18p5 ala May 1998
running on Red Hat 5.1 Kernel 2.0.36.

I will try turning off the oplocks to see if that helps, but I have made
some interesting observations on the problem.

The diabolical Samba share has logical links for company wide, read only
access to various files. These files have world read only permissions. To be
on the safe side, the Samba share is read only as well.

The files being accessed via the share are Lotus 123 V5 .WK4 files. If I
open them from another computer using Lotus 123 V5, I get a repeatable blue
screen 0E exception in VxD Vredir called from VxD IFSMGR. The error message
says it may be possible to continue normally if you press any key. When you
press a key, often you can load the file and continue on.

However, Win98 becomes unstable and locks up sometimes hours later when you
are putting the final touches on your presentation you have to make in 15
minutes.

Today, I tried using Lotus Millenium edition (V9) to access the same files
in the same diabolical share. The error message changed. Millenium does not
generate a blue screen, rather a message box pops up saying the file you are
attempting to open cannot be found on the network. When you click on OK, the
file magically appears in Lotus anyway!!!

The windows clients who own the shared files are routinely and massively
massaging those files all day long with no errors. I don't understand why
sharing them in a common directory via a logical link in another samba share
should cause a networking error.