Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7
Marian, Now i am sure that this is not working(oplocks=no; veto oplock files=/*.doc/*.xls/) at all with Windows 95. No, there are "none" at oplocks with file locks, when oplocks=no. But, when i put oplocks=no and strict locking=yes, this seems to work(at this time, have to test more; i do not know the performance with strict locking). With these settings Excel still uses oplocks, Word approves "none" for oplocks. I can say this only for now, because the problems are not happening all the time only periodically. - Original Message - From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> To: "Hannu Virtanen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 3:01 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7 > OK > when you use smbstatus is oplock active on open files in share with > oplocks=no? > > - Original Message - > From: "Hannu Virtanen" <[EMAIL PROTECTED]> > To: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Thursday, November 21, 2002 12:17 PM > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > > 2.0.7 > > > > Marian, > > I mean that i have started from default settings and tried all off these > > with no help. IRIX has maintenance and feature modes for operating system. > > Only feature mode supports kernel oplocks and i have maintenance > > mode and kernel oplocks are not supported so it is same to have them off > or > > on(on gives very many messages to log-file and this is the reason to have > > kernel oplocks = no at this time. I am now trying these parameters at > share > > level(but i do not understand the difference;i will put all to defaults at > > global section and start with oplocks=no at share level or veto oplock > > files). To change oplock break wait time was an advice in web and said to > > help to these kind of problems with Office 97(10 is also old default > > allthough 0 is default for 2.2.6). We have mostly b and c versions of > > windows 95 and by experiment errors concerns more Windows 95b version(i do > > not know any service packs to go to Windows 95c at all 95 machines). > > - Original Message - > > From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> > > To: "Hannu Virtanen" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Monday, November 18, 2002 4:27 PM > > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in > Samba > > > 2.0.7 > > > > > > > I dont understand what defaults you mean > > > i use smaba 2.2.6 and its default is > > > level2 oplocks = Yes > > > kernel oplocks = Yes(this two is autodetect by samba and > > kernel > > > support by samba docs IRIX have this but you have set NO???) > > > oplock break wait time = 0(samba docs write not change this > > > parameter...) > > > > > > you have > > > level2 oplocks = no > > > kernel oplocks = no > > > oplock break wait time = 10 > > > this your setings is default by your system or set in your conf file? > > > > > > By docs oplocks is share parameter that must by defined in share not > > global. > > > best choice is try use veto oplock files= ... and leave oplocks on. > > > > > > And last what version of W95 you use? W95 W95a W95B ? > > > If W95 then you must update to W95a by service pack from microsoft www. > > > > > > - Original Message - > > > From: "Hannu Virtanen" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Monday, November 18, 2002 12:15 PM > > > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in > > Samba > > > > 2.0.7 > > > > > > > > > > Marian, > > > > All of those are default settings and have been tested not to help. > But > > > why > > > > can i not put oplocks = no, what is standard advice with these kind of > > > > problems. > > > > > > > > Hannu > > > > - Original Message - > > > > From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> > > > > To: "Hannu Virtanen" <[EMAIL PROTECTED]> > > > > Cc: <[EMAIL PROTECTED]> > > > > Sent: Monday, November 18, 2002 12:50 PM > > > > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in > > > Samba > > >
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7
Marian, I mean that i have started from default settings and tried all off these with no help. IRIX has maintenance and feature modes for operating system. Only feature mode supports kernel oplocks and i have maintenance mode and kernel oplocks are not supported so it is same to have them off or on(on gives very many messages to log-file and this is the reason to have kernel oplocks = no at this time. I am now trying these parameters at share level(but i do not understand the difference;i will put all to defaults at global section and start with oplocks=no at share level or veto oplock files). To change oplock break wait time was an advice in web and said to help to these kind of problems with Office 97(10 is also old default allthough 0 is default for 2.2.6). We have mostly b and c versions of windows 95 and by experiment errors concerns more Windows 95b version(i do not know any service packs to go to Windows 95c at all 95 machines). - Original Message - From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> To: "Hannu Virtanen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 4:27 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7 > I dont understand what defaults you mean > i use smaba 2.2.6 and its default is > level2 oplocks = Yes > kernel oplocks = Yes(this two is autodetect by samba and kernel > support by samba docs IRIX have this but you have set NO???) > oplock break wait time = 0(samba docs write not change this > parameter...) > > you have > level2 oplocks = no > kernel oplocks = no > oplock break wait time = 10 > this your setings is default by your system or set in your conf file? > > By docs oplocks is share parameter that must by defined in share not global. > best choice is try use veto oplock files= ... and leave oplocks on. > > And last what version of W95 you use? W95 W95a W95B ? > If W95 then you must update to W95a by service pack from microsoft www. > > - Original Message - > From: "Hannu Virtanen" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, November 18, 2002 12:15 PM > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > > 2.0.7 > > > > Marian, > > All of those are default settings and have been tested not to help. But > why > > can i not put oplocks = no, what is standard advice with these kind of > > problems. > > > > Hannu > > - Original Message - > > From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> > > To: "Hannu Virtanen" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Monday, November 18, 2002 12:50 PM > > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in > Samba > > > 2.0.7 > > > > > > > Try set this > > > > > > level2 oplocks = Yes > > > kernel oplocks = Yes > > > > > > only experimentally. > > > > > > - Original Message - > > > From: "Hannu Virtanen" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Monday, November 18, 2002 9:34 AM > > > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in > > Samba > > > > 2.0.7 > > > > > > > > > > Marian, > > > > Thank for You response. Here is my smb.conf: > > > > > > > > Load smb config files from /usr/samba/lib/smb.conf > > > > Processing section "[homes]" > > > > Processing section "[printers]" > > > > Processing section "[nem]" > > > > Processing section "[ohj]" > > > > Processing section "[proj]" > > > > Processing section "[print$]" > > > > Processing section "[nemadmin]" > > > > Loaded services file OK. > > > > # Global parameters > > > > [global] > > > > coding system = > > > > client code page = 850 > > > > code page directory = /usr/samba/lib/codepages > > > > workgroup = SAMBA > > > > netbios name = > > > > netbios aliases = > > > > netbios scope = > > > > server string = Samba 2.2.6 > > > > interfaces = > > > > bind interfaces only = No > > > > security = USER > > > > encrypt passwords = Yes > > > > update encrypted = No > > > > allow trusted domains = Yes
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7
Marian, All of those are default settings and have been tested not to help. But why can i not put oplocks = no, what is standard advice with these kind of problems. Hannu - Original Message - From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> To: "Hannu Virtanen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 12:50 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7 > Try set this > > level2 oplocks = Yes > kernel oplocks = Yes > > only experimentally. > > - Original Message - > From: "Hannu Virtanen" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, November 18, 2002 9:34 AM > Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > > 2.0.7 > > > > Marian, > > Thank for You response. Here is my smb.conf: > > > > Load smb config files from /usr/samba/lib/smb.conf > > Processing section "[homes]" > > Processing section "[printers]" > > Processing section "[nem]" > > Processing section "[ohj]" > > Processing section "[proj]" > > Processing section "[print$]" > > Processing section "[nemadmin]" > > Loaded services file OK. > > # Global parameters > > [global] > > coding system = > > client code page = 850 > > code page directory = /usr/samba/lib/codepages > > workgroup = SAMBA > > netbios name = > > netbios aliases = > > netbios scope = > > server string = Samba 2.2.6 > > interfaces = > > bind interfaces only = No > > security = USER > > encrypt passwords = Yes > > update encrypted = No > > allow trusted domains = Yes > > hosts equiv = > > min passwd length = 5 > > map to guest = Never > > null passwords = No > > obey pam restrictions = No > > password server = > > smb passwd file = /usr/samba/private/smbpasswd > > root directory = > > pam password change = No > > passwd program = /usr/bin/passwd %u > > passwd chat = *ew*password:* %n\n *e-enter*new*password:* %n\n > > passwd chat debug = No > > username map = > > password level = 0 > > username level = 0 > > unix password sync = No > > restrict anonymous = No > > lanman auth = Yes > > use rhosts = No > > admin log = No > > log level = 0 > > syslog = 1 > > syslog only = No > > log file = > > max log size = 50 > > timestamp logs = Yes > > debug hires timestamp = No > > debug pid = No > > debug uid = No > > protocol = NT1 > > large readwrite = Yes > > max protocol = NT1 > > min protocol = CORE > > read bmpx = No > > read raw = Yes > > write raw = Yes > > nt smb support = Yes > > nt pipe support = Yes > > nt status support = Yes > > announce version = 4.9 > > announce as = NT > > max mux = 50 > > max xmit = 16644 > > name resolve order = lmhosts host wins bcast > > max ttl = 259200 > > max wins ttl = 518400 > > min wins ttl = 21600 > > time server = No > > unix extensions = No > > change notify timeout = 60 > > deadtime = 15 > > getwd cache = Yes > > keepalive = 300 > > lpq cache time = 10 > > max smbd processes = 0 > > max disk size = 0 > > max open files = 1 > > name cache timeout = 660 > > read size = 16384 > > socket options = TCP_NODELAY > > stat cache size = 50 > > use mmap = Yes > > total print jobs = 0 > > load printers = Yes > > printcap name = /etc/printcap > > disable spoolss = No > > enumports command = > > addprinter command = > > deleteprinter command = > > show add printer wizard = Yes > > os2 driver map = > > strip dot = No > > mangling method = hash > > character set = > > mangled stack = 50 > > stat cache = Yes > >
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7
ask = 0744 force create mode = 00 security mask = 0777 force security mode = 00 directory mask = 0755 force directory mode = 00 directory security mask = 0777 force directory security mode = 00 force unknown acl user = 00 inherit permissions = No inherit acls = No guest only = No guest ok = No only user = No hosts allow = 193.94.63. 193.66.15.38 hosts deny = status = Yes nt acl support = Yes profile acls = No block size = 1024 max connections = 0 min print space = 0 strict allocate = No strict sync = No sync always = No write cache size = 0 max print jobs = 1000 printable = No postscript = No printing = bsd print command = /usr/bsd/lpr -r -h -P%p %s lpq command = /usr/bsd/lpq -P%p lprm command = /usr/bsd/lprm -P%p %j lppause command = lpresume command = queuepause command = disable %p queueresume command = enable %p printer name = use client driver = No default devmode = No printer driver = printer driver file = /usr/samba/lib/printers.def printer driver location = default case = lower case sensitive = No preserve case = Yes short preserve case = Yes mangle case = No mangling char = ~ hide dot files = Yes hide unreadable = No delete veto files = No veto files = hide files = veto oplock files = map system = No map hidden = No map archive = Yes mangled names = Yes mangled map = browseable = Yes blocking locks = Yes csc policy = manual fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = No oplock contention limit = 2 posix locking = Yes strict locking = No share modes = Yes copy = include = exec = preexec close = No postexec = root preexec = root preexec close = No root postexec = available = Yes volume = fstype = NTFS set directory = No wide links = Yes follow symlinks = Yes dont descend = magic script = magic output = delete readonly = No dos filemode = No dos filetimes = No dos filetime resolution = No fake directory create times = No vfs object = vfs options = [homes] comment = Home Directories valid users = hkv jyrri read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes browseable = No [nem] comment = Nemetschek Datat path = /usr/nem valid users = nykis1 jaaju kaiju terjo read only = No create mask = 0774 directory mask = 0775 [ohj] comment = Ohjelmatiedostot path = /usr/ohj valid users = +user admin users = admin hkv jyrri force group = sys read only = No [proj] comment = Projektihakemisto path = /usr/proj valid users = +user read only = No create mask = 0774 directory mask = 0775 [print$] path = /usr/samba/printer admin users = hkv write list = hkv guest ok = Yes [nemadmin] comment = Nemetschek Admin path = /usr2/nemadmin valid users = nykis1 jaaju terjo kaiju read only = No create mask = 0774 directory mask = 0775 browseable = No The Office documents are in service [proj]. Hopefully Samba is not only for Linux. Hannu - Original Message ----- From: "Marian Mlcoch, Ing" <[EMAIL PROTECTED]> To: "Hannu Virtanen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 10:06 AM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7 > Hi Hannu > I mean that yuor problem not is in oplock but you change from 2.0.7 to > newest platform and more default values of samba conf is changed in new > version. First you must post to this list your conf that is reply of samba > command > > testparm -s > > afther this anybody can try help you to solve your problem. > Secondary problem is compatibility of kernels that new samba is optimized > for linux. > Try post more information. > Bye. > > - Original Message - > From: "Hannu Virtanen" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, November 15, 2002 9:37 AM > Subject: [Samba] Oplock problems with Office 97 and Windows 95 in
[Samba] Painful question -- nobody answers -- Jerry please answer!
Hello, Please answer to: http://lists.samba.org/pipermail/samba/2002-November/084791.html Hannu Virtanen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Oplock problems with Office 97 and Windows 95 in Samba > 2.0.7
Hello, We have used Samba in SGI IRIX 6.5(now 6.5.11m) machines from the SGI version 2.0.7. We have Windows 95, NT4 and 2000 clients. We had no problems with the version 2.0.7 at all. I am looking for the new possibilities(PDC, BDC and LDAP...) with Samba 2.2.5 and newer. I installed samba.org version of Samba 2.2.5 and from that we have had problems with Office 97 documents in Windows 95 machines. Office freezes and cannot save or create new documents or open existing documents. I searched for this kind of problems from the mailing lists and the web and found out that i am not the only one having problems with oplocks. Why did i not have problems with 2.0.7, is Windows 95 support forgotten from the 2.2.x versions of Samba? The common advice is to put oplocks = no, but this i cannot do, because it means not to use Office 97 from Windows 95 machines(they cannot use any Office documents from the share or create new ones at all), why is that? Is there difference in putting oplocks =no at global or share sections on smb.conf, which kind? Is there a way of telling the client to not ask for oplocks, so that i could disable oplocks from Windows 95 machines? We are now using Samba 2.2.6 with the same problems as 2.2.5 even though there have been discussions of correcting locking problems from 2.2.5, but if this thing was fine allready in version 2.0.7, why does Samba have this kind of fundamental problems? Version 2.2.5 and 2.2.6 have oplock errors also with other programs(F-Secure Anti-Virus, AutoCAD LT 97...), but they does not seem to affect to programs like Office 97. There has been also loss of documents with Office 97 at these situations, when the program cannot save the file(anywhere anymore). I have not heard any problems with Windows NT4 or 2000 clients allthough in the web many have told there ar same kind of problems also with these clients. Hannu Virtanen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
