similar to: Windows XP - samba 1.1.9 slow file transfer problem

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

On 02/09/15 18:06, Luca Olivetti wrote: > Hello, > > my isp provided me with an ont+wireless router combo. > The router can share via samba a mounted usb thumb drive. > The problem is that it's a very old samba version (apparently > 1.9.16p10) and I cannot access it from Linux: > > luca at seis:~$ smbclient -s /dev/null -L 192.168.10.1 > Enter luca's password:

Hello, my isp provided me with an ont+wireless router combo. The router can share via samba a mounted usb thumb drive. The problem is that it's a very old samba version (apparently 1.9.16p10) and I cannot access it from Linux: luca at seis:~$ smbclient -s /dev/null -L 192.168.10.1 Enter luca's password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 1.9.16p10] tree connect failed:

Sorry if this is a stupid question but I tried reading, studying and finding solution but am not making it alone :) On my home lan I have a Linux (Debian sid) box (192.168.174.244) running 3.0.10 samba and cups 1.1.23. My objective is to print from this box to the other home PC which is running XP (192.168.174.242) and sharing an Epson R200 printer. Follows the troubleshooting I could do

Hi, list: Our printers are using samba-3.0.37, and we hit a problem recently when doing file transfer to Windows 2008 Server Clusters. The error occurs when the printer attempts to locate the file path and uses the server IP address rather than the hostname: ====================================================== 18 21.335677 13.121.8.162 13.121.8.3 SMB Session Setup AndX Request,

After upgrading XP to SP2, I can no longer connect to server aliases. The client reports an error 53, "The network path was not found", when doing "net use * \\prof\profile. Mapping to a share on the real netbios name works fine. Anyone else seen this? Setup: samba-3.0.6.rc2 smb.conf [global] netbios aliases = PROF include = /etc/samba/smb.%L smb.prof [profile] path =

Hi, I have run into the following I bonded 6 NICs on my Cent OS server into a 600MB pipe. I use bond method 4 = dynamic Link aggregation. My Cysco Switch 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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have a user who is running a Samba server to store data files for his ArcView 3.3 application. Client operating system is Windows XP professional. With Samba2 (2.2.8a) this was working quite fine, it usually took less than a few seconds to load and render one of the GIS presentations with ArcView. We then did an upgrade to Samba3 (3.0.20b)

We are experiencing some slowness when opening files from a Samba file share using Microsoft Word 2003. Upon examination with Ethereal it became apparent that Session Setup AndX calls are taking a long time to complete, varying from 2 to 8 seconds between the time the client provides an NTLMSSP_AUTH and the server responds. I have also noticed a peculiar NetBIOS name query for

I trying to figure out why copying from a Samba drive to Windows XP is slower than an FTP transfer beween the same two machines. To copy the 110 MB file from Samba takes 400 seconds, and to transfer the same file by FTP takes 41 seconds. From using ethereal, and comparing a fast smb copy to a slow smb copy, I can see that the slow copy has a _lot_ more tcp traffic for a SMB single read

I tried to close everything I had open and filter as best as I could.. but left random lines in just in case it helps. 172.16.5.230 is my local machine and *.33.235 is the server. This is a slow save.. 13:48:39.852340 (60) 001F5B35DB28 Broadcast UDP - Other Ports 172.16.5.93 172.16.5.255 00:04:53.922946 293.922946 13:48:39.852605 (60) 001F5B35DB28 USC-IANA

Dear all, My question is described as follows. Server: Linux Samba-3.3.1 Client: Windows XP with SP3 Step1: connect to the samba server. Step2: select a directory name ?test?. (The directory is created before testing.) The client will send a lot of QUERY_FILE_INFO requests. According to data captured by Wireshark, I find the following phenomenon: The client repeats exactly the same

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

After migrating a particular W2K file service to Samba 3.0.21c on SuSE 9.3 Pro (a DMS with winbindd against a W2K3 ADS), the W2K clients are suffering performance issues (in a switched LAN). Looking at the traffic with Ethereal (latest SVN), it looks like the client writes the data in *1 byte* pieces likes this (c=client, s=server): c->s NT Create AndX Request c<-s NT Create AndX

Hi! I'm currently hunting a strange problem and looking for help! I have a samba3 fileserver (currently samba-3.0.20b, but problem can be reproduced with samba-3.0.7, but _not_ with samba2 like 2.2.8a), and I see performance problems when writing files with MS word 2002 SP3 from a NT4.0 (SP6a) workstation. Saving even the smallest file takes more than 10 seconds! Copying files with Windows

Hi, We're doing some of performance tests with Linux Samba v3. We're comparing WinXP/Win2k clients vs OS2 clients accessing a samba server. For one test, we're coping 10.000 small files. Let's say, we run the command copy \\sambaserver\10000files\*.* c:\data\10000files With an OS2 client it takes 23 seconds to complete. With an Windows client it takes 460 seconds to complete.

Hi all, I'm running version 3.0.28a on Ubuntu linux, and apparently from a day to another I got performance issues: without any change in smb.conf (except a few added shares) I have mac osx and linux clients getting a very slow upload/download speed. I've checked with other protocols, like scp and performances are good, so I can exclude a network/hardware problem. Other clients are

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

I see *things* happening here. XP. Trying to access \\host\sharea. works fine \\host\shareb - pops up password window shares a and ba may vary between reboots. I spent 15 minutes scratching my head and finally tossed out "snoop port 445" So what I've seen. On shares I can access wxp do: 1. Send: Tree Connect AndX Request \\host\sharea 2. Receive: Tree Connect AndX Response 3.

Hello, my company recently changed the stucture of some shares (Win2000). Since then, we are not able to access these shares from Linux/Solaris anymore. I tried smbmount and smbclient and can access the top-level directory of the share and see the directory structure, but I can't see any data inside these directories. A few days ago, someone told me that msdfs is used for the new structure