similar to: Socket Errors

I have four samba servers connecting into a samba PDC (using ldapsam as password backend) and all of the servers get the "transport end point not connected" error. I've looked in the groups but cannot find anything that helps. I've tried to set my oplocks=no and other similar settings but nothing seems to help. The only thing that seems to limit excessive sleeping smbd

I've recently setup an iSCSI portal on my network and have taken some servers offline. However, due to the requirements of certain software programs I need to use UNC paths. I was able to fix this issue by adding CNAME into my DNS. I'm still finding that certain programs still require to view the browse list to find the appropriate server. Since CNAME doesn't link to the

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]

I have a probleme with my samba server. I have a lot of closewait socket state causing the load average to increase. Samba generate some errors logs but I don't know the signification of "Signal 7 in pid xxx". For information, I am running a samba 3.0.10-1.4E.2 under a kernel Linux version 2.6.9-22 with a RHEL 3.4.4-2. Here is the log file (/var/log/messages) :

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 :

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

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 all, I have been working on a multi-domain network (2 of them) with one domain being controlled by Samba/Openldap config and the other a standard Win2k AD. I have had success getting all computers on the Samba domain to see the Win2k controller via the Network browser but it does not seem to be working the other way around. My network config is split up into two separate VLANs using an

I'm attempting to join a Samba 3.0.4 domain on a Debian linux box, with a Windows XP client. Problems 1) Can only get the join to work if I use the root account. On Win2k I can use any account in the Domain Admins group. 2) The join succeeds, the unix account and the smb account are created but the smb account is disabled, and the password contains all XXXXs. Joining the domain works

I was wondering if anyone has come across an error in their winbindd log: could not lookup membership for group rid S-1-5-21-3506869558-4124343851-970148941-2025 in domain BOGUS (error: NT_STATUS_NO_SUCH_GROUP) I have all the mappings done correctly: domainadmin (S-1-5-21-3506869558-4124343851-970148941-512) -> domainadmin domainusers (S-1-5-21-3506869558-4124343851-970148941-513) ->

I have 3 Linux rh9.0 servers on the network all using Samba/LDAP to authenticate. One is acting as the PDC and the other two are domain members. On one server I don't have winbind running and everything works great, however, on the other server, if I turn off the winbind I get a password prompt and cannot access the server. I have no need for winbind but I'm forced to keep it on.

Hey, I have a samba 3.0.0. PDC on my Fedora Core server. I have one win 98, one XP and one NT clients. As I log on, I get "primary gid of user [username] is not a Domain group" error. I am sure gid is 100 (users) and my add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u If I login using the root account, I don't have this problem. What can I do to fix

We are running Redhat 9, 2.4.20-30.9 kernel, Samba 3.0.0 and Winbind 3.0.0. Security is set to "Domain" and we are trying to set up shares which will be available to valid NT 4.0 users and groups. Winbind appears to be working, and you can use the commands "getent group" and "getend passwd" to see that it is communicating with the NT domain for user and group

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]

Hello! I faced with the following error message when I try to add a Unixware (2.1.2 i386 x86at) to windows 2000 domain (I have already added the computer to the domain), samba version 2.2.8: dab> smbpasswd -r CCS -j GEOMANT -U lhever -s Password: write_socket_data: write failure. Error = Socket operation on non-socket write_socket: Error writing 72 bytes to socket 0: ERRNO = Socket operation

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