similar to: Syslog error messages

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]

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

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,

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

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 =

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)

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

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]

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]

I'm trying to upgrade from Samba 3.0.14a to 3.0.23b. Using the exact same config file that I did in the older version, and using the exact same share directory and file permissions as I did with the old version, a share that I used to be able to access now returns: tree connect failed: NT_STATUS_ACCESS_DENIED When I try to connect to my home directory that's shared on the fly, I

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

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

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

Hi , We use redhat 8 . Samba is 3rc2 Smb.conf is workgroup = TEST server string = %h server (Samba %v) null passwords = Yes passdb backend = ldapsam:ldap://X.X.X.X /,guest passwd program = /usr/bin/sudo /usr/local/samba/bin/ldapsync.pl %u passwd chat = *Envoyez* %n\n *modifying*entry* unix password sync = Yes log level = 2

Hello everyone. I think Samba is wonderful. I have a full domain running here using ldap servers as the back end. The PDC connects to the master LDAP server while the BDC's do localhost lookups as they are slave LDAP servers. The following are snippets of logs that are appearing on my syslog host. Error is on top explanation below. Could anyone point me in the right direction? I am running

Hello, I have two machines (Samba under Linux, and Win98) that try to connect to another samba machine. They are all two seen as UNKNOWN machines. With the Linux one, I am correctly authenticated, but with the Win98, Connections are rejected. Here is a level 3 log file (It's a bit long, sorry). As you can see, there is an ERRNO = Connection reset by peer Thanks.