similar to: closewait socket state

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]

Hi. Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have added will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont

Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have add will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont understand:

It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,

I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23

Hi, I'm running samba 2.2.7 on redhat advanced server with approximately 40 win2k clients and having a serious problem with the clients. Intermittently the clients will lose their connection to the server for approximately 30 seconds. It's like the socket connection is being reset or something. Here's a sample output from a client log file: [2003/04/12 15:13:08, 0]

This is probably a hot topic, and if this has been beaten to the ground, forgive me. I'm not a regular part of the Samba community. Although I have been using Samba for years, I now have to use it in a corporate environment utilizing some of it's more modern features. Let me just say, that it's been several hours of testing/troubleshooting to get where I am now. (And I don't

A few times in the last couple months we have had our production Samba 3.0.14a-1server crash. We did not have detailed logging turned on at the time so the attached output of our log is the best process tracking I can give at the time of the crash. What will happen is our shares will no longer be accessible, and all the smbd processes will be hung. We can ssh to the server and do a restart

Hello, I run a samba (v3.0.10) PDC and openLdap server on the same machine. They work fine, except sometimes the smb server cannot contact the ldap server. From a windows client, it looks like the server gets stuck, and it takes a few minutes before the shares are available again. In the /var/log/messages file, i get these error messages :

Greetings, I have a File Server, Running Samba on RedHat 7.0 Everything Works fines, It have 64 megs of ram, and around 15 peoples using it. But sometimes, in the morning when people try to access it's Share it gives the error msgs: NETWORK IS BUSY. All my user get logon using a Windows NT PDC. To enable my user to connect to Samba, I "play" with the computer for a While..

Hi ! I need help ! I installed Samba 3, and many files are corrupting. I have many error lines in my logs. -------------------------- machine log file: -------------------------- [2003/11/03 10:38:06, 0] lib/util_sock.c:write_socket_data(388) write_socket_data: write failure. Error = Broken pipe [2003/11/03 13:36:15, 0] lib/util_sock.c:write_socket_data(388) write_socket_data: write

Hello, I'm having some trouble with the winbind process I'm getting a lot of error: [2005/07/04 14:14:48, 0] libsmb/clientgen.c:cli_send_smb(155) Error writing 494 bytes to client. -1 (Broken pipe) [2005/07/04 14:14:48, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435) cli_pipe: return critical error. Error was Write error: Broken pipe [2005/07/04 14:14:49, 0]

We have an environment where Linux workstations use Windows domain controllers to authenticate everything, from SMB access from Windows workstations, to graphical logins, and ssh. We've been seeing some intermitten failures with the authentication for SMB access. Here are some samples of the error messages we're getting. [2005/02/15 01:03:24, 0] lib/util_sock.c:write_socket_data(499)

I've just moved our school's library database from a Windows NT machine to a FreeBSD 3.4-STABLE machine running Samba 2.0.6 installed from the port. I've had a lot of files become corrupted since then. The support house that has had to repair these files, said that the beginning and end of the file are there, but there's a big gap of nulls in the middle. I'm using log level

Good Afternoon, I have Samba 2.2.1a running on a SPARC Solaris 2.7. All of a sudden I'm having a problem with one PC mapping Samba drives. In the log file for this PC I get the following error messages: [2001/12/11 12:47:22, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2001/12/11 12:47:22, 0] lib/util_sock.c:send_smb(729)

My printer works ok under samba 2.0.7 but from time to time (about twice a say) users can't print. I found this in logs: [2001/04/09 21:20:38, 2] smbd/connection.c:utmp_claim(560) utmp_claim: conn NULL [2001/04/09 21:20:38, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2001/04/09 21:20:38, 0] lib/util_sock.c:write_socket(566) write_socket:

Some of the computers in our network keep having trouble connecting to samba I was able to restore the connectivity by placing the computer and IP address in the host file. Immediately after that the client was able to connect. It is my understanding that when Samba is using WINS if the WINS server fails to respond within a certain length of time then these are the types of errors I will get. Is

(Server :Mandrake 7, Samba 2.0.6) (Client : PC Win95 and Win 98) Samba's work fine since one year but yesterday We had a big problem in my college Lots of PC's client can't connect (invalid password). In the samba's log we read : > [2000/05/19 12:15:21, 1] smbd/service.c:close_cnum(568) > renoir (192.168.84.189) closed connection to service valancee > [2000/05/19

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 all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server