similar to: netbios-ssn problem

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)

Sorry if this is such a basic question but I couldn't find anything about this in the FAQs/HowTos/Digest. I've compiled samba-1.9.18p3 on SunOS4.1.3_U1. When I tried to run smbd via inetd.conf (SIGHUP), I always get the following on the console. inetd[590]: netbios-ssn/tcp: unknown service I've edited the /etc/services to add: netbios-ssn 139/tcp And the /etc/inetd/conf with

Hello, (Samba 3.0.21c / Linux 2.4.27) a smbd process was hanging on a file server since one day. This smbd process was locking some files on the server, and that was causing some share violation for a Windows user (well, that what I think). I did a lsof on the smbd process, and I saw that the TCP netbios-ssn connection was still seen as established with the machine of the windows user that

Ahh, many sleepless nights spent on a stinky Windows 98 box! I'm using Samba 2.2.0 with Red Hat Linux 7.1, and am having trouble resolving the samba server. I went through the "fault tree" in the "Using Samba" book, and this was the section I got stuck on. Do I need to be running a name server besides nmbd? nmblookup returns some results: ----------8<----------

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..

I administer Samba 2.0.7 on Debian Linux (kernel 2.2.17, libc6 2.2). When trying to mount samba shares from Windows 98 workstations sometime the process failed with error message: [...] [2001/02/12 17:32:21, 1] smbd/server.c:main(641) smbd version 2.0.7 started. Copyright Andrew Tridgell 1992-1998 [2001/02/12 17:32:21, 1] smbd/files.c:file_init(216) file_init: Information only: requested

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:

for months, we keep fighting issues with smbd (now at released 2.2.6), config is with spoolss, domain logon, and the client in question is an NT4 machine. server is a i386/linux 2.2.19 For a very long time, we thought it was related to oplocks, but now after having them disabled, it still is there. Level 3 Log is as follows: [2002/10/22 17:08:18, 3] smbd/ipc.c:reply_trans(480) trans

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:

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]

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

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

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]

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'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]

Greetings. Is there something up with Samba and RedHat, or with recent kernels, or with some packages that have been updated recently? A lot of us seem to see the same login errors with samba and I have yet to get my windows clients to login to my new samba server. The log messages really don't help. I had an old server running Samba 2.0.7 (RedHat 5.0 upgraded to nearly 5.2 with 2.0.33).

(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

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