Guys, unfortunately i left linux for the most part about 3 months ago (i went to windows). I already miss linux and making one latch ditch effort to try to figure out what was going on. Though i don't think it matters i was in general running ubuntu strains of linux (ubuntu, lubuntu, ubuntu mate). I did have a short stint on arch.

My biggest issue that made me leave was network issues with a windows server file server. Everything is on a gigabit lan with cat 7 wired everywhere. Everything has intel gigabit nics. I would have to say i spent at least a month of my time (no exaggerating) trying to get the speed of samba to an acceptable level. Sometimes i would spend 3 days at a time (staying up late) trying different things to get a descent speed. I researched all kinds of different smb.config configurations but alas nothing worked(messing with options like tcp_nodelay to no avail) Sometimes i would get 50-60 Mbps. Which although i wasn't thrilled i was able to live with at the time only for randomly the speeds to decrease to 8 Mbps for no apparent reason ( no changes). I hoped for a patch one day that would fix the issue.

I also messed with jumbo frames and for some reason on linux it made things worse. One time i decided to try a broadcom nic and it was actually faster than the intel nic (but not much). My testing pretty much entailed using Nautilus and see what kind of speed i got when reading/writing a large file (usually larger than 1GB) to the windows file server. Reading/Writing for both equally bad.

Throughout the years i went from 14.04, 14.10, 15.04, 15.10, 16.04, 16.10, 17.04 (when i left) and the bad network speeds never improved. Window server versions changed from changed from 2012, 2012 R2, 2016 and that had no effect either. When i changed my workstation to windows 10 (same hardware speeds) with 9k jumbo frames enabled. My speeds are now 105-120 MBps which is what i would expect. I would think samba would come out of the box with at least decent network speeds but thats not what i've found.

I'd like to go back to linux but i can't live with these horrible networks speeds anymore. The file server must remain windows server. Does anyone have any clue or does the samba speeds between windows/linux just suck? I've seen many post with people with the same issues and have seen a few (according to the post) that figured it out but many that haven't. I would think with how many enterprises use linux servers this couldn't be a general problem but then again i never tried to use linux as my samba server.

Nautilus uses Gnome's virtual filesystem GVfs that includes a backend gvfs-smb for accessing SMB/CIFS shares. Yes, many complain that using GVfs is slow.

From the first bug report it looks like a libsmbclient problem. Many people mount the share via mount.cifs versus using Nautilus/GVfs to get better performance. I do not know if there is a real fix yet.

The smb.conf file is used by the server not the client so it has no affect on Nautilus.

https://en.wikipedia.org/wiki/GVfs

https://bugzilla.gnome.org/show_bug.cgi?id=738535
https://bugzilla.gnome.org/show_bug.cgi?id=762384

I want to thank you SOOO much. Here is a big *virtual* jug. I'm sad and happy at the same time.

Happy because thankfully I won't be wasting any my time on smb.conf anymore. For some reason, i thought smb.conf affected the client too but apparently, i was wrong. At least I know what is wrong now and don't keep on having to guess. Not knowing just plain sucks.

I'm sad because the countless hours I spent on this problem that I will never get back. Oh well, i guess that's how it goes.

After googling I'm particularly surprised this has never been fixed. It has been out there for at least 5 years (if not longer) and apparently no one has attempted to fix the issue. I'm sure there are plenty of enterprises that have had this issue and that's where pressure is usually applied. At least I know what the issues are now and I'm going to have some things I'm going to try. Would maybe fixing the issue be as simple as using an alternative file manager? Have any suggestions? Maybe Konqueror?

I might chime in again here if i have any more questions when i'm trying to see if i can get around the issue and hopefully go back to linux.

Almost sounds like doing it backwards, using Windows for the server and Linux for the desktops. Most people do it the other way around. My wife's windows laptop gets 70-80MBs over wired when pulling from a samba share on my server, maxes write speed on her spinner hard drive. My guess is this is a Windows problem and not a Linux problem as they have been known to intentionally gimp things they don't like or see as competitors. Is just a guess of course but it wouldn't surprise me. Maybe try putting a linux file server in a vm if you can't bare metal it and see what kind of speeds you get then. That would answer it real quick.

That is NOT true and lilbelous. You need to be careful what lies you spread.

You can avoid using GVfs (or the KDE equivalent) by creating an entry in /etc/fstab, using the cifs file system. This is sort of the equivalent in Windows of mapping a drive letter to a network share. A little bit of set up effort, but you get good performance from then on.

https://wiki.ubuntu.com/MountWindowsSharesPermanently

If you do NOT want it to be a "permanent" mount, use the "noauto" flag. It will then show up as an unmounted drive that you can still manually click on to mount/browse.

Libel by definition is lies about a person, not a thing.

I go by personal experience + what I read online. You can't go 2 posts without reading various things especially with networking. Samba printing, worked great until Windows 10 then magically doesn't work, and MS has the nerve to say it's a samba problem. It is clearly their problem and an intentional one at that. Network transfers between the 2, half the speed of Windows > Windows. People have problems between the two all the time. I've had countless problems with my wifes windows laptop and everything else in the house being linux.

I know you like that word. I've seen you use it in other posts. Make sure you use it correctly next time.

There you go again.!!