similar to: Failed to set socket option

Dear friends, I receive the error "Error Bad file descriptor" when samba start, the socket option in smb.conf have the line: "socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=4096" My distribuition is Red Hat 6.2 and the Samba version is 2.0.69. This is the error log /var/log/samba.smb: [2000/08/31 14:07:06, 0] lib/util_sock.c:set_socket_options(148) Failed to set

Hi there everyone, Again another slight thing I noticed since I upgraded to Samba 2.0.6 from 2.0.5a. I'm using RedHat Linux on a Celeron 400 with kernel 2.2.13. My socket options in smb.conf is set to "TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUF=8192 SO_RCVBUF=8192". However I've started getting the following everytime I SIGHUP to reload the configs and stop-start:

Hello all, I receive some errors which I cannot explain : Hopefully there's someone who can help me. When I type: "smbclient -L 10.33.6.180" I get: Session Request to 10.33.6.180 failed (code 0) Session Request to 10 failed (code 0) Session Request to *SMBSERVER failed (code 0) What does code 0 mean? Log.smb shows problems with socket-options: But I haven't changed these

Hi, My Samba server (Solaris 7, 64-bit mode) with AFS option has been running for a year. I just changed the "Max Log Size" global parameter few times today. Each time I committed the change, I got the following same set of error messages in my Samba log (the log.smb file): [2002/01/03 17:40:56, 0] lib/util_sock.c:set_socket_options(151) Failed to set socket option

Hello! I was using samba-2.2.0-alpha3 (and just about earlier versions as well) and had no problems with getting W2K users to login to my domain using their username/password. However, after upgrading to samba-2.2.0, when W2K users tried to login using their username/password, W2K pops up a small dialog box in the middle of the screen that says - Your account has been disabled, please

Hi there everyone! One of the users complained to me that yesterday, he suddenly couldn't access the network. He was online the whole day, then suddenly at around 6:45pm he couldn't write. A restart of his workstation rendered him completely disconnected from the Samba domain. Server is running Samba 2.0.6 on a RedHat 6.0 machine with Linux kernel 2.2.13. Client is running Windows95 OSR2

I am seeing the following errors under Samba 2.0.6/Solarisy 7. I saw discussions of this on the Samba list but couldn't find any resolution. I saw the following message from Jeremy Allison > Message-ID: <387B949C.B499EC9C@valinux.com> > Date: Tue, 11 Jan 2000 12:37:48 -0800 > From: Jeremy Allison <jeremy@valinux.com> > Subject: Re: Error when

I've two files server on Solaris 2.8 on which i've samba 2.2.8a fonctionnal I've try samba 3 on one server and now my users from windows NT can't mount there unix home via samba here a copy of smb.conf # Global parameters [global] # Definitions des parametres globaux workgroup = grovsdma netbios name = grovss01 server string = Samba sur %L security = share # Demande a

I'm getting some strange error messages on my Samba server. Does anybody know what these mean, or where I can look them up? I also don't -think- I'm getting the performance I should be. Any help is much appreciated, Craig Pentium II-300Mhz 128MB RAM Solaris 2.6 Samba 2.0.6 Intel 10/100 NIC Running at 100Mb/Full Duplex Clients are mainly WinNT 4.0-SP4 running ArcView. Feb 27

Hi all, I've built samba 3.0.22 on solaris10 sparc with ldap support using thes config parameters : ./configure --prefix=/opt/samba \ --localstatedir=/var/lib/samba \ --enable-socket-wrapper \ --disable-cups \ --with-privatedir=/etc/samba/private \ --with-piddir=/var/run \ --with-configdir=/etc/samba \ --with-logfilebase=/var/log/samba \ --with-ldap \ --with-ads=no \ --with-automount \

I'm having serious problems with Samba not working properly. Clients can't log into the server for some reason. I'm trying to run through the diagnosis stuff at http://us1.samba.org/samba/docs/DIAGNOSIS.html and when I try to do a net view \\samba-server at a pc DOS prompt, I get 'System error 1728 has occurred. A remote procedure call (RPC) protocol error occurred."

I sent an earlier message asking for help in debugging the cause of this error. I didn't get any response. Today, I set debug level to 10, shutdown and started samba, and waited for the error to occur. The error did re-occur but I have 12460 lines of log to search through. What should I be looking for (I didn't want to send the log to the list)? > Date: Tue, 11 Jan 2000 12:37:48

Folks: I have a strange issue that occurs when one of my XP Pro system tries to connect to a samba server (2.0.24) on either a Sparc Solaris 10 or Sparc Solaris 9 system. This is the output from log.smbd when the problem XP Pro system tries to connect to the server: [2007/03/28 14:47:01, 0] lib/util_sock.c:get_peer_addr(1229) getpeername failed. Error was Invalid argument [2007/03/28 14:47:01,

I am new to Samba, having just taken over management of a HPUX system in a mainly Windows environment. The system is running Samba 3.0.7. I am getting the following errors, repeatedly, in my log.smbd. What does it mean? Is this actually a problem or normal chatter for Samba? If it is a problem, what should I do to correct it? [2006/05/03 07:41:38, 0] lib/util_sock.c:set_socket_options(202)

Hi, In the last a couple of weeks, Eric helped me fixed a couple of my new samba 3.0.5 running on HP-UX 11i hang issues. Right now, people still experience slowness when they run some applications on the samba shares OR recursive list directories on the samba shares. There was not a lot of errors in the individual log files. However,there are some errors in log.smbd and log.0.0.0.0 file. 1)

Hello experts After a total panic last weekend, now my LDAP+Samba is working fine, apparently. However, in my syslog, each one minute, still occurring errors like this: Apr 25 08:47:21 myserver smbd[10245]: [ID 702911 daemon.error] [2005/04/25 08:47:21, 0] lib/util_sock.c:set_socket_options(202) Apr 25 08:47:21 myserver smbd[10245]: [ID 702911 daemon.error] Failed to set socket option

I am using Samba 3.0.20 with Sun Directory Server as a PDC. I have been running this setup for a year now, and I haven't had any other issues, except this one... I have four Windows 2003 Servers that are domain members. On one of the 2003 Servers is being used as a Terminal Services Session Directory, and the other three 2003 Servers are Terminal Servers. I am trying to add the three

[2000/05/07 09:29:39, 0] lib/util_sock.c:set_socket_options(148) Failed to set socket option SO_KEEPALIVE (Error Bad file number) [2000/05/07 09:29:39, 0] lib/util_sock.c:set_socket_options(148) Failed to set socket option TCP_NODELAY (Error Bad file number) THese errors appears in log.smb, WE cant print threw the smb shared printers THe version is samba-2.0.7 on solaris 6 & 7 PLease

I have Linux Server 7.0 running Samba with 1 nic ip 199.168.1.2 and the Win2k server with 2 Nic one having the DHCP ip from the DSL and other being my internal 199.168.1.1, Now I installed samba and setup a smb.conf file smbd and nmbd runs fine also testparam doe's not show any errors and when I run the smbclient on the same machine It's authenticates fine, but when I try to access

Hi, a few months ago I posted a message about using LDAP to store rsync secrets in LDAP. I received a response about patching the rsync source code with a patch file. I am now finally getting around to doing this, and when I tried to use the patch command 'patch --verbose ./rsync-2.5.6/authenticate.c rsync-ldap.patch' , it gives me the following error: Hmm... Looks like a unified diff