That's the way it works, as far as I remember. I'm not familiar with fake oplocks, but we use something similar (turning them off -- might be the same command aliases, actually -- not sure). Office does not play well with oplocks.
---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630 On Wed, 21 May 2003, Joern Krebs wrote: > > Hi, > > I have the following problem: > (I'm not sure if have to send this message to you, or to Microsoft. ;-) > > Samba 2.2.3a or 2.2.8a (not restarted yet) > Network of Windows NT 4.0 PCs and > one Windows 2000 Server. > > The Windows NT Workingsations are working fine, but now I have to > integrate an Windows 2000 Server and with this Server I have the > following problem. > > When I open an XXXXX.doc-file Office 97 tells me, that the file is > already openend by the same User. When I open an XXXXXX.dot-file > everything is O.K. And after enabling "fake oplocks" for this share > everything is also working fine on XXXXX.doc-Documents. > > I think I can live with this fake oplocks (hopefully there won't be > two users working on the same file), but after I am responsible for > the system this is not a satifying solution. > > Does anyone know the problem or has an other solution. > > Ciao, Joern! > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba