similar to: Slowness problems with Samba 3.0.1, Solaris, and Clearcase

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

Hi All, I am having a problem with Samba that seems to be a bug. I say this because I read the archives and they described a problem similar to mine and were told that it was a bug in older version of Samba and the latest version should have it fixed. I am running what is essentially a RH 7.3 on a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5 and am using the following

Hello list, I've got a problem concerning locking of files with a share on a nfs mounted NAS. samba server is 2.2.8a installed from SuSE-RPMs the NAS is mounted with following line in fstab: <IP-Number>:/vgroup00/data02/data /mnt/nas01 nfs rsize=8192,wsize=8192,soft 0 0 I tried to save a file from word which lead to a aprox. 1 minute hang of my Win2k/SP3. The log of the

Sorry if this issue has come up before. I have been using samba on a NetApp filer successfully for some time but I recently upgraded my samba server to Suse 9.0 Professional. I am trying to use the 'classic samba' version (since I don't know any better) and am having problems with file locking on my shares. Here is a transcript of the log.smbd that shows some incompatibility between

Hi, Is there a known issue with FreeBSD 5.2.1 and Samba 3.0.4? I am getting file corruption when copying to a local FAT32 drive (mounted under FBSD) from a Windows XP Pro workstation. There doesn't seem to be any pattern in the corruption. If I mount an UFS drive, everthing is fine. I'd also like to find out if the corruption would also have affected file updates, and not just new file

Hi, I run a Veritas cluster server with two different samba's 2.0.7 compiled with SUNWspro 4.0 (gcc 2.95 leads to the same results) on Solaris 7 UltraSPARC 60 server. One compiled with --prefix=/opt/samba-test the other with --prefix=/opt/samba-eng. To avoid using 127.0.0.1 or 0.0.0.0 when both smbd's running on the same cluster host I set this in both smbd.conf

I was trying to copy swf file (35MB) from a windows machine to my samba share. It told me "There is not enough disk space". However, it lets me copy it in another share. I didn't notice anything different with the share I am having problem with. I noticed the following messages in the log: [2005/08/10 13:56:47, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING:

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)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 2GB of transfer, files stop being written by Samba. I keep getting Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(656) Jun 12 11:29:37 nasserver smbd[8715]: posix_fcntl_lock: WARNING: lock request at offset 558761983, length 1 returned Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37,

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

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

There seems to be a few people having this problem, but not much response. I've dug into the logs, and while I don't know exactly what I am looking at, I think I may have found something that may make sense to someone. A short recap. Samba was working fine, until I did a Debian security update, which upgraded my Samba to 2.2.8a. Now, I can create files on a mounted Samba share in a

I am using 3.0.13 and have temporarily run out of disk space on the main samba server, so I have NFS mounted some space from another machine. into a directory that is accessible under samba. When I try to save directly from ms word 2003 sp1 (and same from word 2000) it tells me: on the win98se and win xp pro sp2 clients: "Microsoft Office Word" Word cannot complete the save due to

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)

Well, next problem. Because of samba isn't running on alphaserver 1200 with gentoo linux and kernel 2.6.9-ac12 i've simply exported my smbroot (on alpha, it is my fileserver) and have samba running on an intel pentium4 box, also gentoo, kernel 2.6.0-ac12. Seems to work, eccept some locking problems. smbd[9450]: [2005/02/08 17:29:51, 0] locking/posix.c:posix_fcntl_lock(657) smbd[9450]:

I ran into this problem and was unable to find a solution here or in google. Thought I'd post it to the list so maybe it'll help someone out in the future. Gentoo Linux running 2.4.22 and Samba 2.2.8a. ReExporting an NFS mounted share on a NetAPP fileserver connected to eth1 via samba out eth0. All PCs are able to write fine but when writing to the share via a mac using OSX the

Hi all, I've got kind of strange setup, wherein all of my data is on a big NFS server (RH linux 8.0 running the 2.4.18 kernel and nfs-utils 1.0.1-2.80) and my Samba 3.0.0 PDC server (RH linux 7.3 w/ 2.4.18 kernel, nfs-utils 0.3.3-6.73) mounts the NFS export with the following options: rw,vers=3,wsize=8192,rsize=8192,hard,intr This mounted partition is then re-exported to the windows users

We are receiving the following in our logs: Mar 18 13:41:37 athena smbd[24222]: [2005/03/18 13:41:37, 0] locking/posix.c:posix_fcntl_lock(658) Mar 18 13:41:37 athena smbd[24222]: an Invalid argument error. This can happen when using 64 bit lock offsets Mar 18 13:41:37 athena smbd[24222]: [2005/03/18 13:41:37, 0] locking/posix.c:posix_fcntl_lock(659) Mar 18 13:41:37 athena smbd[24222]: on 32

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