similar to: oplock_break: MS kb articles

Recently Microsoft introduced some network improvements which made it impossible to connect to Samba without using encrypted passwords. There is a way-around for NT4.0 (SP3) by changing a registry entry. This has been published by Microsoft in their knowledge-base. With WIN95 OSR2.1 and the vredir patch (vredir.vxd and vnetsup.vxd dated June, 2nd 1997 or later) the behaviour is very similar to

Thank you for contacting ServiceWare Support Services. Please consider this response as confirmation that your email has been received. Your inquiry has been logged into our case tracking system and assigned to a Support agent. ServiceWare Support agents respond to email cases Mondays through Fridays, 8am - 6pm US EST (excluding holidays). If you are currently experiencing a high priority

I'm hoping someone can help me with a problem that's driving me potty! I have a network at home of various flavour of Wind*ws and a Mandrake 8.1 Linux box. After much trial and error, I have set the sytem up so I can log on to the network from WIn NT, Win 2k, Win 98 - but, no matter what I try, I cannot get a Win 95 machine to connect. I have installed the vrdrupd.exe file on the Win

Hello, I have a problem width some excel files in my Samba File server because when I try to open from a WinMe client, the client machine always craches width a error in the vredir.vxd and ifsmgr.vxd. I think is a problem in oplocks or something like that. In the mdb files, the MS Access tolds me that can't open the file exlusively! Can anybody help me? What configuration should I have in

Ok, anyone know if we're subject to the same bug as MS fixed in 95B vredir.vxd? A test, with log level 3, sound like it's in order. --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | //www.oreilly.com/catalog/samba/author.html Work: (905) 415-2849 Home: (416)

-- Please note: ----------------------------------------------------------- Any of the following options will transfer your e-mail directly to my desk. (Do _not_ enter the ' signs! They are only used for clearity here.) a.) Save my address under 'Rainer Hantsch' in your address book or use 'Rainer Hantsch <office@hantsch.co.at>' in the 'To:' field... b.)

This only happens with PCs on the other end of a bridged 56k DDS line. It also affects DOS and W98 clients the same. Clients can log onto the domain ok, and browse. But trying to drag a file, or even right-click it in W98 explorer, cause the machine to hang, and eventually blue screen with a VREDIR VXD error. If I copy to Samba, sometimes it works, but then the file is zero bytes. Copying from

The updated Vredir.vxd file corrects a problem deleting files on Samba servers running on UNIX- based computers. This problem can cause local files to be deleted. (168936 bytes, published 07/16/97 ) http://www.microsoft.com/isapi/support/ps_sl.idc?purl=/windows/&pfx=w95&base=windowssupport&kbd=win95x&sl=q_misc95 Hope this helps, Alan

Hi everybody, I already posted a similar message sometime ago regarding performance problems when various user are trying to share a common Microsoft ACCESS MDB file. Thank you for the messages I received regarding this problem. Unfortunately I still haven't managed to find a solution. It looks like this performance problem is also visible if you try to access any file already open by another

I have SuSe 7.0 newly installed, with default/networking packages installed. It is installed on 2nd partition (Win2k on starting cyl's) and use floppy to boot Linux. It is a 333MHz Celeron, 128Mb Ram, 30Gb drive 1/2 for win, 1/2 for linux - lots of room =) I have a Kingston EtheRx KNE100TX adapter, running CAT5 to a LinkSys BSFR41 Cable/DSL router. The only way i could get the network to run

Joel Handler wrote: > Date: Thu, 8 Jun 2000 16:50:33 -0400 > Subject: Netscape error > We are having a problem with Netscape that every so often we get lanman > redirector errors. We have Netscape 4.73 setup so that the users home > folder is located on the samba server (H drive). Do you know have any > ideas. The errors pop up randomly and have yet to be > pinpointed

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

Hi! Even with 2.0.4, I'm still seeing a lot of oplock break failures (clients failing, see log further down). The client hangs for approx 30 secs (sometimes more) and then gets back online. At least one user can't use the file shares at all; it hangs whatever he does, and on any computer he uses (NT or 98, laptop, desktop...) Other users have less problems, but maybe they are less

2.0.4b, RH60 (2.2.6+raid1, non root-raid), accessed from win98/ie5. Intermittently ie5 takes very long to load an html page from samba; at the same time it loads another html page ok from another linux/samba1.9.x At 10:47:34 I click on the html page and it is loaded at 10:48:18. [1999/06/23 10:47:34, 1] smbd/service.c:make_connection(488) go (10.0.0.115) connect to service go as user go

Concerning the question "Why on earth do I see the dosChDir to /home/girgen/ports???!" you might check out how you *start* or *started* Samba. Based on my observations, and a quick check of the source code (see source/smbd/server.c, and source/smbd/uid.c), when you start up smbd, it finds out the current directory, saves it as "OriginalDir", then whenever a new user is setup,

Many 2.0.x users have the: [1999/06/23 10:47:48, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:47:58, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:48:08, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:48:18, 0] smbd/oplock.c:oplock_break(790) oplock_break: receive_smb timed out after 30 seconds. problem. I get this

Sorry for all my emails. I don't know where to post this problem, so I also post it to the ntdom mailing list... Since I upgrade to 2.0beta5, I got a lot of messages like this in log.smb: [1999/01/08 16:30:38, 0] smbd/oplock.c:(734) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file GN/previsions/previsions 99/previsions globales 99.xls (dev = 800073,

We are running Samba 2.0.5a on an AIX 4.2.1 box, and since we upgraded from 1.9.18, a Windows 95 client reports intermittent problems (timeouts) when saving small files. The log.smb file has entries from those events: [1999/09/08 14:59:07, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:17, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:27,

I've been seeing these in my logs files ever since I upgraded to 1.9.18p10 and turned on oplock support for users' home directories: --snip -- 1998/10/07 10:05:44 oplock_break: receive_smb timed out after 30 seconds. 1998/10/07 10:05:44 oplock_break failed for file Start Menu/Open Office Document.lnk (fnum = 14, dev = 808446, inode = 45cb8). 1998/10/07 10:05:44 oplock_break: client

Dear Samba users, I've had a problem recently with Samba (2.2.3a, and now 2.2.5) on my OpenBSD 3.1-stable Installation. Bsd: OpenBSD 3.1-stable (CYNOSURE) #1: Fri Oct 4 01:06:45 EST 2002 avant@XXXX:/usr/src/sys/arch/i386/compile/CYNOSURE I get problems such as these: <poor formatting> [2002/10/13 23:00:04, 0]