similar to: Samba 3.0 ACL, Windows Credentials

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

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,

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]

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)

Hey all, I've got an issue with my Samba server. I can't seem to get file shares to map using Server Name, but I can get them to map using IP Address. Here is my smb.conf: [global] workgroup = ADMIN server string = Snap Server timestamp logs = yes dos filetimes = yes dos filemode = yes inherit acls = yes name cache timeout = 0 winbind uid = 101-6000000 winbind gid =

Dear All, we are experiencing severe problems with Samba 2.2.0 (with quota support) running on a dual processor (400MHz) Sun E450 running Solaris 2.7. This is used as a central file server for student diskspace, accessed by approx 1200 PCs running NT 4. Up until recently we experienced some, what we assume to be, loading issues with connections during the middle of the day being slow.

Hi Kristis, Kristis Makris wrote on Friday, 18 July 2003 9:19 a.m.: > [2003/07/17 12:16:06, 0] lib/util_sock.c:get_socket_addr(900) > getpeername failed. Error was Transport endpoint is not connected > [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket_data(388) > write_socket_data: write failure. Error = Connection reset by peer > [2003/07/17 12:16:06, 0]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 knorr smbd[5439]: [2003/10/31 10:27:02, 0] lib/util_sock.c:get_socket_addr(919) knorr smbd[5439]: getpeername failed. Error was Transport endpoint is not connected knorr smbd[5439]: [2003/10/31 10:27:02, 0] lib/util_sock.c:write_socket_data(388) knorr smbd[5439]: write_socket_data: write failure. Error = Connection reset by peer knorr smbd[5439]:

hi list, i try since weeks to authenticate my linux-clients against my samba-server. This works very fine with 2 windoze-cliens. but i still cannot authenticate with my linux-clients. i am @office now, thats wy i ask instead to test: i heard, winbind is used to authenticate linux-clients against the samba-server. the wbinfo -u gives me back: DOMAIN-user (i use the minus as separator) so i

Hello, I originally posted this on samba-technical (http://lists.samba.org/pipermail/samba-technical/2003-July/046076.html), but I just verified that I'm also seeing the same error message with samba-3.0.0beta3. I have not tested if I'm also getting disconnects and Word saving problems that way. But, people using 2.2.7 must have also seen this. Here are some messages I've seen in

Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]

Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 +toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]

Hi folks, today I tried to switch from a samba 2.2.2 PDC to a samba 2.2.7 PDC. Everything semed to be working fine with smbclient. Windows user couldn't log on, but with following differences: * users belonging to the domain admin group could log on from Win2k boxes * normal users couldn't log on from win2k boxes, with the usual "check if you didn't mis-type

My syslog is constantly bombarded with these messages: Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:get_socket_addr(1012) Mar 27 07:15:35 fileserver1 smbd[70359]: getpeername failed. Error was Socket is not connected Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:write_socket_data(499) Mar 27 07:15:35 fileserver1

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

My log files are getting quite big because of all the errors I get in a day. Here is a snipet: Jan 27 10:03:06 localhost smbd[17694]: [2004/01/27 10:03:06, 0] lib/util_sock.c:get_socket_addr(919) Jan 27 10:03:06 localhost smbd[17694]: getpeername failed. Error was Transport endpoint is not connected Jan 27 10:03:06 localhost smbd[17694]: [2004/01/27 10:03:06, 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:

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