similar to: Broken pipe errors can result in corrupt files ==> please help

Hello, After upgrading a host from XP/32 to Windows 7/64, I see the following entries in the logs, what is the root cause of this issue? Nov 14 10:10:18 l1 smbd[6174]: getpeername failed. Error was Transport endpoint is not connected Nov 14 10:10:18 l1 smbd[6174]: write_data: write failure in writing to client 0.0.0.0. Error Broken pipe Nov 14 10:10:18 l1 smbd[6174]: [2009/11/14 10:10:18,

Bonjour, I'm running samba 2.0.4 on a Sparc Solaris 2.5.1 and I have some error logs when I'm trying to connect to a sharing directory from *some* NT4 WS (SP4 or SP5): pchp2 (194.xxx.xxx.xxx) connect to service centreAS as user truc (uid=1326, gid=1320) (pid 22939) [1999/08/26 15:52:57, 0] lib/util_sock.c:write_data(415) write_data: write failure. Error = Broken pipe [1999/08/26

I'm hoping to get some guidance diagnosing intermittent smbd errors that have been cropping up in the last 2 months. They are sporadic, difficult to reproduce, and don't reveal much of a pattern so far except that the majority are generated by a couple of clients, although several clients appear to be affected. Typical symptom on the client is a hang when attempting to look at the share

Over the last few weeks I've had problems using Samba on a FreeBSD. Windows XP clients (that's all I have) would experience intermittent long delays (lockups, freezing) when accessing the samba shares using Windows Explorer or any other applications. This occurred both directly when browsing the network neighborhood, and when accessing the share through a letter drive mapping.

Guys, After upgrade to samba 3.3.4 on openSuSE 10.3, I'm getting: Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bonza

Suddenly in the past week we have been having users who share excel files via our Samba complain that the file has become corrupt, and also some database files (Orcad .tdb database files). Fortunately there has in each instance been a good copy in the .recycler... so far. I came across some docs and threads in the net about oplocks. I did find an error in the samba log: [2008/04/14 10:19:05,

Hi !! I have already sent this message to the list, but, as I have not received any replies, I am trying again !! I have Samba 3.0.22 running as PDC on solaris10. Each time a windows client (XP SP2 or W2003) opens an explorer to access a share, I see in the log.smbd : [2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Invalid argument [2006/06/15

I get the following errors in log.smb: [1999/02/24 17:02:44, 1] lib/util_sock.c:client_name(810) Gethostbyaddr failed for <CLIENTs IP> [1999/02/24 17:02:44, 0] lib/util_sock.c:write_data(407) write_data: write failure. Error = Broken pipe [1999/02/24 17:02:44, 0] lib/util_sock.c:write_socket(191) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [1999/02/24

Dear Sir(s), I just posted the same message But managed to find the answer within 30 minutes of posting In your smb.conf, in the [globals] section add Max xmit = 8192 Socket options = TPC_NODELAY I hope this will fix your problem too ! Beat regards Terence

Hi samba lists !! =20 =20 I=A1=AFm found error message Windows XP =A1=B0The network name cannot be found" When I try to connect to smb server that is mapped e: =20 1. I was downloading very large file 40GByte with torrent during 5 hours. 2. This error occurred!=20 3. But web server and telnet is OK 4. I retry to reconnect to smb server with IP

Hello, This morning my users started complaining that they could not log in to the network. When trying to log in people get a long pause and then a message that the password was wrong, or there was no machine to authenticate them. When I check the logs I get the following errors: [1999/04/22 08:18:37, 0] lib/util_sock.c:write_data(407) write_data: write failure. Error = Broken pipe

Hi, our window file server running 3.0.25b-33 (X64) (Sernet rpm) on SLES 9 SP3 has been stoped working. The log file shows nothing new. No error ... Only the clients can not connect to the server. After a restart of smbd it seems to work for a while. Any idea ? Any help is welcome !! ---------The last logline before was 10:39; at10:42 no connection was possible----- Jan 7 10:42:30 modena

Hi, I'm having a problem accessing my samba server from Windows. The problem occurs every time I try to browse to it on either XP or 2003 Server. The error message I get is: "\\Zeus is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to log in

Hi, Our samba server is running Red Hat Enterprise Linux ES release 4 (Nahant Update 4) with samba version: samba-3.0.33-0.17.el4. We like to authenticate all the users with our Primary Domain Controller wnidows 2008. Some users keep getting asked to enter username and password. Even with the correct password, still can't access the drive. The strange thing is that some users are

Hi list, Since I've upgraded from Version 5.0 to 5.1 i have strange problems with samba. Since 5.1 the connection from a XP client to the samba server disconnect often, especially then i write a file to the share after some idle time. Some informations of my config. The Box is a Samba PDC for a little Windows Domain with a ldap backed. I used this config on Centos 4.x and 5.0 without

Hallo, on a school server in the neighbourhood Samba 3.0.22 (only SMB server, "security = server") serves many Windows2000/XP clients in their classrooms. The last lesson on a friday ends at 13:35, then the pupils shut down the clients and leave the room. In /var/log/warn follows -------------------------------------- Sep 7 13:39:37 Arktur smbd[31514]: read_data: read

I have a lab with 24 pc's I'm trying to reimage. I have a DOS network boot disk (version==win98) and all clients connect to the Samba share. When I start the image download with xcopy, the session appears to hang immediately. With one or two, a small amount of hard drive activity will continue, but the file copy will fail. When I connect to a win2k share on similar server hardware, I

I'm doing some testing with Win7 RC1 and I'm having an identical problem with two CentOS servers (5.2 and 5.3) both running Samba 3.0.33 where I cannot authenticate. Both servers are authenticating with Winbind to an AD DC. I have a third CentOS 5.2 server with Samba 3.0.33 shares that does not use Winbind which has no problems. This pops up in smbd.log: (.200 is wireless and .184 is my

hi all, i have a Samba version 3.2.5 server running in a debian 5.0.8 (a little old, i know...). the network setup is: -one local office using samba -one remote office (we call it cberg) using samba remotely over a vpn (linksys-cisco) -another remote office (we call it colon) using samba remotely over a vpn (linksys-cisco) the local office and colon office are working fine the remote office

Hello, We use samba to backup some (rather large) sql databases. Lately we ocasionally are getting fail reports, as in the file could not be written, and windows generating an error 64: "The specified network name is no longer available" While going trough the logs, i can see the following error (sorry for the long output): ----- [2008/05/19 01:14:46, 0]