search for: so_sndbuff

-----BEGIN PGP SIGNED MESSAGE----- Your mileage may vary, however I have found this to be a very reliable method of determining the optimal "socket options" values for SO_SNDBUFF and SO_RCVBUFF. 1. Adjust your smb.conf to reflect: socket options = SO_SNDBUFF=4096 SO_RCVBUFF=4096 TCP_NODELAY IPTOS_LOWDELAY 2. Kill your smb/nmb processes, and restart samba. 3. From a workstation, download and install siSoft Sandra (http://www.3bsoftware.com/Downloads/sandra/sandra.html)...

...don't see how it would become a problem on Windows XP clients, but not on Windows 2000 clients. I've already tried changing the socket options parameter in the global section of the smb.conf file on the server. It previously was set to TCP_NODELAY, and I tried a setting of IPTOS_THROUGHPUT SO_SNDBUFF=8192 SO_RCVBUFF=8192. Any suggestions? Would upgrading to Samba 3.x resolve this issue? Thanks for any input. Greg Adams

I am having some unresponsive and very slow performance with a couple of different file types with Samba and Windows 7 clients. The problems manifest in the following manners: IGES files, these are CAD files. When opening up certain IGES files from the server, the application can take upwards of 10 minutes to open up the file. If I copy the same file from the server to the desktop, the

...supports this apparently. However I only get increased bandwidth from my MAC by connecting via AFP. However when I connect via SMB I don't. I was told to change the sockect options to the following on my smb.conf file on my fileserver: socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUFF=2048000 SO_RCVBUFF=2048000 large readwrite=yes read raw= yes write raw= yes I did these changes and still top out at 53 MB/s however via AFP I am able to get an average of 90MB/s up to tops 103MB/s. It seems really odd that I cannot tweak SMB to utilize the pipe properly. Any ideas on what settin...