similar to: kernel oplock and broken pipe messages

I have a problem with samba 2.05a on my irix-6.5 box. Now I know this must be a user problem because I have run samba on this machine before. Samba compiles and runs fine and I have tried the precompiled version too. I have /tmp shared out as [tmp] and get the following messages in log.smb when I try to connect to it using smbclient from the localhost smbd version 2.0.5a started. Copyright

I posted a problem with oplock previously, but am guessing it goto lost in an earlier thread with the same subject line, so here goes another shot: Using Samba 3.0.22 on a Gentoo box (kernel 2.6.15) I've a situation where file locking does not seem to be functioning as expected, in that more than one user can open and write to a file without any notifications being displayed about the file

Hi guys I have that config in global section of smb.conf: kernel oplocks = No locking = Yes oplocks = No level2 oplocks = No strict locking = No veto oplock files = /*.pdf/*.PST/*.pst/*.doc/*.xls/*.docx/*.mdb/*.MDB/*.dbf/*.DBF/*.ppt/*.xlsx/ I restart the service and I am still getting that log: [2010/12/23 11:16:24.105806, 5]

Hi: I am running Samba 1.9.17 at SUN Solaris 2.6 and it works well. After I upgrade Samba 2.0.3 or 2.0.5a, my Excel spreadsheets got trouble. In the Samba log file I got: [1999/08/23 10:45:32, 0] lib/util_sock.c:write_socket_data(570) write_socket_data: write failure. Error = Broken pipe Anybody has an idea what is the problem? I

Hi there everyone! One of the users complained to me that yesterday, he suddenly couldn't access the network. He was online the whole day, then suddenly at around 6:45pm he couldn't write. A restart of his workstation rendered him completely disconnected from the Samba domain. Server is running Samba 2.0.6 on a RedHat 6.0 machine with Linux kernel 2.2.13. Client is running Windows95 OSR2

Hi again Volker (& list) I think I am very closer of the problem. Look at this please # A file is deleted => OK [2015/03/06 07:31:45.359108, 2] smbd/open.c:704(open_file) expl opened file PRENSA_Avance1_20150306_070500.pdf read=No write=No (numopen=1) [2015/03/06 07:31:45.359145, 5] smbd/oplock.c:92(set_file_oplock) set_file_oplock: granted oplock on

I run samba 2.0.6 on Sun ultra enterprise 2 server. Lately the logs have been filled with [1999/11/29 20:11:19, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [1999/11/29 20:19:31, 0]

Have searched through the mailing list archives and have seen this show up a couple of other times, but no answers seem to be forthcoming. I am runing Samba 2.0.6 on a Red Hat 6.0 system and keep seeing the following errors in the logs: lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = broken pipe followed by: lib/util_sock.c:writewrite_socket(563) write_socket:

Hello, I've been searching through the Samba archives attempting to find a resolution to intermittent Win2k -> Samba 2.2.2 for IRIX share failures. It seems that there have been numerous failures similar to mine reported with various versions of Samba and various OS's, but I've been unable to find a workable resolution. Intermittently when connecting to a Samba share from Win2k

Okay, here's the background. Fedora Core 4, all recent updates. Using samba-3.0.14a-2. Trying to mount a remote shared folder, and sharing it for local users in my office. Using /etc/fstab to auto-mount it on bootup. Here is the /etc/fstab line that I use to do this: //share/ccc /gobo smbfs username=XXXXX,password=XXXXXX,uid=10395,gid=30038,fmask=770,dmask=770 0 0 I use winbind to

I have successfully compiled OpenSSH 3.1p1 for the following systems: Solaris 8 Solaris 7 Irix 6.5.14 Irix 6.5.4 SunOS 4.1.3_U1 Unfortunately, the new sshd is not working on any of the above systems with the exception of Solaris 7. (I then put the Solaris 7 executables on Solaris 8, and they worked there too.) This is the error I'm getting: $ /usr/etc/sshd -D -d -d -d debug3: Seeing PRNG

Hi, The only reason I use Samba is I want to connect my linux desktop with my windows laptop and share the larger disk with the laptop. I got weird problem that I could only write to the samba server but I could not read from it with errors like: [2001/03/04 16:36:38, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2001/03/04 16:36:38, 6]

I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst

Dear All, We have successfully run 1.9.18p2 on our AIX 3.2.5 servers since 1.9.18p2 was released, with heavy access for printing and file sharing from users and NT servers. We are currently in the process of upgrading to AIX 4.3.2 (now completed) and have been trying to implement 2.0.5a. I have used the AIX binary install which all worked. We are using WINS/DNS/DHCP running on the NT servers

Hi everybody, I'm writing for an any help. I tried some news groups about linux etc... nothing :-( On our normaly working network unexpectly starts this problem. Win clients don't see smb server. See logs below: log.nmb [2002/03/11 09:37:33, 1] nmbd/nmbd.c:main(757) Netbios nameserver version 2.0.10 started. Copyright Andrew Tridgell 1994-1998 [2002/03/11 09:37:33, 0]

Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store

A rather distressing timestamp issue (to multiple users here). Anyone seen similar behavior or have a suggestion/solution? Problem: Opening and closing an excel file (no changes/keystrokes to file) on the Samba server causes the file to be saved with time stamp of closing. (There is no autosave set on Excel - also see other info below) MS Excel 97 SR-2 NT 4.0 SP5 Solaris 2.6 or 2.7 (2

I am getting the following error from smbclient and am not sure as where the problem is. smb: \gcc\> dir write_socket_data: write failure. Error = broken pipe write_socket: Error writing 91 bytes to socket 3: ERRNO = broken pipe failed session setup Error writing 91 bytes to client. -1. Exiting This appears to be happening about a minute after I establish a session. Up until that time file

William E. Dent will be away from Wednesday August 30, 2000 to Tuesday September 5, 2000. Mail is being forwarded to wedent@home.com. Original Message Text follows: ---------------------------------------------------------- Send samba mailing list submissions to samba@lists.samba.org To subscribe or unsubscribe via the World Wide Web, visit

>What are you actually using for authentication ? We are using Quest Authentication Services (formerly Vintela Authentication Services), which is a Kerberos/LDAP/Active Directory client for UNIX & Linux. Authentication and Identity Mapping appears to work correctly, I can log on and see my uid/gid/correct groups list with SSH and group-based access for files and directories appears to