similar to: Random share disconnects

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

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]

Hi, I compiled Samba 3.0.7, MIT Kerberos 1.3.5 and OpenLDAP 2.2.17. I did not notice any errors during compilation. I searched and found the #define HAVE_LDAP 1 and #define HAVE_KRB5 1 statements in the config.h file of Samba 3.0.7's include dir. So, ADS should be supported in the compiled Samba 3.0.7 version. Here is what I did up to now. As described in the How-To Samba doc, I created

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

Hi There... I guess i got a simmilar problem as Collen. I configured my samba3 with mysql as PDC. I can add users and connect with them to the shares. Even the Workstation account is created automaticaly. But if i try to logon to this domain Win2k tells me: "The system can't logon to the domain.... the Workstationaccount is missing in the domain or the password for the

===INFO=== Server: Fedora Core 2, Samba 2 Client: Windows XP, all TCP incoming ports firewalled, outgoing TCP permited Problem: Cannot join to domain ===SHORT-LOG=== write_socket: Error writing 5 bytes to socket 23: ERRNO = Connection reset by peer ===FULL-LOG=== [2005/09/21 17:56:44, 0] lib/util_sock.c:write_socket(455) [2005/09/21 17:56:44, 2] lib/access.c:check_access(324) Allowed

===INFO=== Server: Fedora Core 2, Samba 2 Client: Windows XP, all TCP incoming ports firewalled, outgoing TCP permited Problem: Cannot join to domain ===SHORT-LOG=== write_socket: Error writing 5 bytes to socket 23: ERRNO = Connection reset by peer ===FULL-LOG=== [2005/09/21 17:56:44, 0] lib/util_sock.c:write_socket(455) [2005/09/21 17:56:44, 2] lib/access.c:check_access(324) Allowed connection

Was just browsing web and tried to save some files on a samba share and got: permission denied 3 times in a row... (and now on 4th try, it worked). The log for the past hour looks a bit odd... why so many module reloads? wouldn't they load once? Also I've never seen the "New VC == 0, if NT4.x compatible we would close all old resources." Why would I get so many session

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

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

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)

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

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

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]

(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

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