I have been struggling with this one for a while. I've searched and read a ton of posts about it at various Linux-related sites, and none of the advice (like setting socket options and other parameters in samba.conf) has helped. Some of them made it slower, but none improved the speed beyond what I had been getting before playing with any of the parameters.
I've narrowed the scope of the issue to Samba shares that are mounted through the Nemo GUI on the client machine. It does not matter whether the server is running Windows or Mint... if the client is Mint and the share is mounted via Nemo, I get ~50% of the throughput expected. When I reboot into Windows on any of the client machines, I get all of the speed expected from the same hardware and the same server.
This slowdown happens on all three PCs I have Mint on, whether using the gigabit ethernet or wireless (Intel and Realtek gigabit, Atheros, Intel, and another Intel on wireless). I tried a live USB with Kubuntu on it, and I got the same result using Dolphin: half the expected speed.
I knew the underlying TCP speed was fine, since FTP connections and transfers were as fast as expected, and when I tried using smbclient to access the shares from the terminal on the Mint PC, the results were good (all the expected speed) there too.
As one site suggested, I tried unmounting the share with the Nemo gui and then mounted the share from the terminal with this (replacing the xxxxxx and .x.x. with the appropriate values, of course):
Code: Select all
sudo mount -t cifs -o username=xxxxxx //192.168.x.x/Shared /mnt/TEST-SHARE
I was then able to open that share in Nemo and initiate a copy with the usual drag and drop, and I got the full throughput expected.
So... while I now have a workable means of getting the full speed through Samba, I would like to know if there is a way to get Nemo to do whatever it was that made the command-line mount quick? The way Nemo does it automatically is quite convenient, and I would like to be able to use that if it is possible.