similar to: WinXp - Samba - Solaris Connection issue

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)

All, I see recurring error messages in my "smbd" log file. Any ideas how to fix this? [2010/01/29 09:17:27, 0] lib/util_sock.c:set_socket_options(261) Failed to set socket option TCP_NODELAY (*Error Invalid argument*) [2010/01/29 09:17:27, 0] lib/util_sock.c:set_socket_options(261) Failed to set socket option IPTOS_LOWDELAY (*Error Invalid argument*) [2010/01/29 09:17:27, 0]

Greetings Experts! Sorry for my poor english, but I?m inside of a terrible nightmare!!! I?m using Samba+LDAP has about 2 months ago without problems, but in the last 4 hours, the system is absolutelly unstable. I couldn?t upgrade or patched anything. The problem simply has appeared. Principally system characteristics: - Sun Fire V880 running Solaris 9 - openldap-2.2.23 - nss_ldap-232 -

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

Hi !! I have already sent this message to the list, but, as I have not received any replies, I am trying again !! I have Samba 3.0.22 running as PDC on solaris10. Each time a windows client (XP SP2 or W2003) opens an explorer to access a share, I see in the log.smbd : [2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Invalid argument [2006/06/15

Greetings, all We've been running samba2 for far too long - I'd just never found the time to upgrade, and it wasn't a priority since it WORKED. Our little Solaris9/SPARC64 box happily served our few gigs of files to 20 users, and played the part of a PDC. Then I upgraded CUPS, and discovered samba2 doesn't like cups-1.2 libs, and figured it was as good an excuse to make the

I'm finally getting somewhere in setting up my FreeBSD PDC. I try and login via my XP client and now it gives me this odd message. "Cannot login because a duplicate user already exists on the network. Please goto control panel and system and change your computer name." Sorta paraphrased there, perhaps off by a word or two but that's pretty much what it tells me. I'm just

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

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

A couple weeks ago I upgraded my servers from 3.0.14a to 3.0.24. My main server generally has about 800 to 1200 people connected to it at any given time. Its a Solaris 8/Sparc system, samba is configured as security = domain . Everything seems to be functioning fine, I haven't noticed any odd behavior, haven't had any complaints. But, a few weird errors have got me concerned. 1) I

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:

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

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

Hello -- I recently installed Samba 3.0.1 on our Solaris 8 servers (as well as our RedHat servers) and I wanted to see if I could get some feedback on a few things. We are using Samba in conjunction with Clearcase for our software developers and because of that, we have oplocks turned off (also level2 oplocks = no as well). We are authenticating to our ADS server, but joining the domain with

Hello List, I have a bit of a strange problem with an OS 10.3.3 XServe (Samba 3.0.2) that I've inherited from a previous sysadmin ;). It's a bit hard to describe but I'll do my best and include applicable log files and the smb.conf. Ok, first of all this machine is bound to our Active Directory domain and authenticates users there (security = ads). It uses the Windows 2000 DC

[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

Hi there, Since upgrading our debian sarge boxes to 3.0.23c, we have found that we are unable to connect to shares using the official hostname of the servers (short or fully qualified) but can still use its netbios aliases (again, short or fully qualified). As nothing else has changed in our configuration, I think that the change of behaviour is down to the newer release and can find nothing in

I have built samba 3.0.4 on Solaris 9 and it appeared to compile and build OK. It starts up and runs with a PDC smb.conf. It becomes the brows master for the domain and generally seems to look OK. However, when I try to join a PC into the domain I get "Invalid argument" logged by set_socket_options() in lib/util_sock.c when trying to set TCP_NODELAY and SO_KEEPALIVE. This is

I'm having problems using Microsoft Access 2000 mdb files on a Samba share. The same database worked very well on a Windows server. I had hoped Samba would be a drop in replacement for a Windows server but apparently Access needs special Samba configuration. In Access I sometimes get Run-time error '3035': System resource exceeded. I don't see any errors in the log file when