-
All replies
-
Helpful answers
-
May 22, 2016 12:09 AM in response to Samplexby adamclark182,I've had the same problem with SMB, my iMac and MacBook Pro won't connect since upgrading to 10.11.5. I'm connecting using CIFS as temporary fix but it's not ideal.
-
May 22, 2016 4:26 AM in response to Samplexby lucadamiano,Same problem here! I used to transfer my printer's scans to my iMac using SMB but, since upgrading to 10.11.5, the printer reports a connection error.
-
May 22, 2016 7:48 AM in response to lucadamianoby AgentMax81,Same problem.... Cant use AFP because its unstable and is causing random unmounting network drives.....
-
May 22, 2016 7:50 AM in response to Samplexby BobHarris,Everyone, Please report this to Apple. The more direct reports, the more likely this will be come a priority.
BugReporter
<http://bugreporter.apple.com>Free ADC (Apple Developer Connection) account needed for BugReporter.
Anyone can get a free account at:
<https://developer.apple.com/register/index.action>
AndMac OS X Feedback<http://www.apple.com/feedback/macosx.html>
The feedback link is easy, but it would be better if BugReporter were used.
And
If you are still have Apple Care, that channel would be good as well.
-
May 22, 2016 12:04 PM in response to Samplexby TimAnanas,Same Here, MBP early 2015 + WD MyCloud.
CIFS works well. But TimeMachine does not.
-
May 22, 2016 12:05 PM in response to BobHarrisby Ibanezq,Yesterday I sent logs of my NAS to Western Digital support.
Thread @ WD Community site:
https://community.wd.com/t/updated-to-osx-10-11-5-my-cloud-unusable-in-finder/16 4186
-
May 22, 2016 11:40 PM in response to Samplexby donazipe,Does NOT work if I connect to the WD MyCloud drive through smb as a registered user or as guest (finder very slow, spinning rainbow wheel, error "can't copy error code -8058"). Tried to connect through afp, it does work.
Another sad "me too"... :-(
(clearly, all this after updating to 10.11.5)
-
May 23, 2016 3:36 AM in response to Samplexby emmanuelg75,Same pb here with a Sinology NAS DS215j...
I had to switch to AFP to get speed back, but wow... every update become a adventure....
-
May 23, 2016 10:27 AM in response to Samplexby ChisolmLee15,Some observations and testing suggestions.
Behind the scenes, network devices are often / sometimes busy negotiating with each other over who is who, what they'll do (indications of what services each device is running, etc.), who is the boss (egs.: SMB [Local | Domain] Master Browser) re some priority / protocol(s), and more.
If there is a / are Windows OS device(s) on your network, it / they can tend to bicker a lot over who will be the boss . . . especially when SMB network activity is involved (egs. again: SMB [Local | Domain] Master Browser).
If you do not have any Windows OS devices on your network, then consider NOT enabling SMB/CIFS on your NAS device. In other words, keep the amount of protocols running, to a miniumum of what your Mac OS device(s) need, such as AFP. Also consider not using FTP/SFTP connections to your NAS device. IOW, if you're using only Apple devices, stick with AFP.
I'm looking at the Synology NAS knowledge base, their help article:
Help Articles > Control Panel > File Sharing > File Services > Win/Mac/NFS - DiskStation Manager
There is a lot of good info there.
First, it may help you to Disable Opportunistic Locking. (In Samba language, in the smb.conf file, you'd adjust/create the "oplocks" setting(s).)
If you Disable Opportunistic Locking, then be sure to also disable "Transport encryption mode" --- the Synology NAS KB article states:
Transport encryption mode: When SMB 3 is enabled, Windows File Service will add transport encryption to strengthen file transmission security.
- Disable: No transport encryption will be applied.
- Auto: Transport encryption will only be applied to clients supporting this feature.
- Force: Transport encryption will always be applied. This will cause clients that do not support transport encryption to be unable to use Windows File Service.
Apple's SMB 3 implementation in the later Mac OS (egs. El Capitan) is no doubt for security. But, the two settings, when ENABLED:
Opportunistic Locking
Transport encryption mode
might be causing performance problems. Disabling these two features, would be a temporary fix until Apple and/or NAS developers iron out the difficulties.
There is a third setting in the Synology NAS KB article that you might consider: making the Synology NAS device your network's Local Master Browser. You might test your connection and data backup / copying performance, with that feature enabled / disabled.
The Synology NAS KB article says:
Enable Local Master Browser: When multiple Windows computers exist within the same subnet, they will negotiate and elect one computer as a "local master browser." The local master browser maintains lists of the other computers within the subnet and their shared resources, and shares these lists with the other computers. This option allows the Synology NAS to assume the role of local master browser.
Adding to that:
Note: Enabling this function disables hard disk hibernation and activates the guest account without a password.
Overall, you'd be testing / tuning the NAS device, in order to improve data backup / copying performance, while you accept the risks of testing and any temporary fix.
I'm guessing that Apple "improved" some SMB 3 feature --- yet another security consideration now comes with attendant restrictions --- and that is why the connection and data backup / copying performance has become more troublesome.
Some tips re connecting:
In the Finder, use Command + k keys - to produce a Connect to Server window.
When connecting to an SMB serving NAS device, use its network IP address (make sure that the NAS device has a fixed IP address on your network).
The share on the NAS device - make sure that its name is 8 characters or less, and all capital letters - for example "SHARENAS".
Make sure that your network users who connect to the NAS device, are registered in the NAS device, with usernames that have NO SPACES. For example, if your Mac's user account shortname is "johndoe", then use that and 'as is', meaning all lower-case characters. Do not set up users in the NAS device, such as "John Doe" or "Elizabeth Doe".
The reasons behind all that, is/are, that it helps sometimes to stick with old Samba Server / SMB / NETBIOS conventions.
Now, in the Connect to Server window, let's say your network NAS device's IP address is 192.168.3.2, and its network share is named "SHARENAS" --- type:
smb://192.168.3.2/SHARENAS
and click the Connect button.
Other settings in that Synology NAS KB article . . .
"Veto files" - I'd disable that.
"Apply default UNIX permissions" - I'd disable that, and test.
"Clear SMB cache" - I'd routinely click that, in order to clear caches.
"Enable SMB 2 with Large MTU" - You might not want that. Which reminds me, that elsewhere on your Mac, in System Preferences > Network . . . you can set the MTU value for your network location setup; try 1424 (default has been 1500 - but it can lead to some failures to get complete packets from A to B in a manner of speaking; this setting (value of 1424) has helped with AFP over/thru VPN connections).
"Enable SMB 3" - The Synology NAS KB article states: "SMB 3 supports AES-based file encryption transmission, thus improving the security of peer-to-peer file transfers." You might try testing without that enabled.
-
-
May 23, 2016 11:05 AM in response to ChisolmLee15by ChisolmLee15,I meant to add this:
"Workgroup" - You might consider creating a Group (System Preferences > Users & Groups). Let's say that you name your Group: "GROUPNAS". Set that up in the Synology NAS device, too. Might help with the connection and the resolution of file and folder permissions work being done aboard the NAS device. I describe how to set up a Group in another reply, another topic here.
-
May 23, 2016 11:17 AM in response to Samplexby Krutsch,Firmware update released today for WD MyCloud devices. Connects faster from the Finder (i.e. connects to shares quickly, like it used to).
However, still no improvement in read/write throughput. Using BlackMagicSpeedTest, I am seeing read spends over GigE of roughly 33 MB/s, as opposed to the 75 MB/s I used to see with SMB to my Mac Mini from a MyCloud 3TB, prior to the last Mac OS X update.
With AFP read speeds vary from 40 - 60 MB/s (it's all over the place with AFP).
Thanks, Apple!
-
May 23, 2016 12:01 PM in response to Krutschby MajorIP4,Krutsch wrote:
Firmware update released today for WD MyCloud devices. Connects faster from the Finder (i.e. connects to shares quickly, like it used to).
However, still no improvement in read/write throughput. Using BlackMagicSpeedTest, I am seeing read spends over GigE of roughly 33 MB/s, as opposed to the 75 MB/s I used to see with SMB to my Mac Mini from a MyCloud 3TB, prior to the last Mac OS X update.
With AFP read speeds vary from 40 - 60 MB/s (it's all over the place with AFP).
Thanks, Apple!
There's no mention in their firmware notes as to this specific problem. Did it fix mounting as SMB and seeing files within the mounted share? Only AFP works for me.
-
May 23, 2016 1:28 PM in response to MajorIP4by Krutsch,MajorIP4 wrote:
Krutsch wrote:
Firmware update released today for WD MyCloud devices.
There's no mention in their firmware notes as to this specific problem. Did it fix mounting as SMB and seeing files within the mounted share? Only AFP works for me.
Correct. I noticed that, as well. I changed from using "smb://..." to "cifs://..." to mount shares and that fixed my problem, with respect to mounting.
I don't know why AFP is faster now, but it may be just because everything was rebooted. I really hope there is some resolution to the SMB performance issue, because 2x decrease in speed will be tough to live with.
-
May 23, 2016 2:30 PM in response to Krutschby MajorIP4,Krutsch wrote:
MajorIP4 wrote:
Krutsch wrote:
Firmware update released today for WD MyCloud devices.
There's no mention in their firmware notes as to this specific problem. Did it fix mounting as SMB and seeing files within the mounted share? Only AFP works for me.
Correct. I noticed that, as well. I changed from using "smb://..." to "cifs://..." to mount shares and that fixed my problem, with respect to mounting.
I don't know why AFP is faster now, but it may be just because everything was rebooted. I really hope there is some resolution to the SMB performance issue, because 2x decrease in speed will be tough to live with.
So I connected command+K cifs:// and although it now shows my files here's the Get Info:
-
May 23, 2016 2:36 PM in response to MajorIP4by Krutsch,Interesting... same result (I never thought to look at Get Info for the mounted share). So, maybe the cifs://... thing is a red herring.
All I know is: my WD MyCloud SMB shares were pretty speedy and, post latest Mac OS X update, they are dog-slow.
I'm sure Apple is thinking about "security" with their changes for SMB3, but my in-home NAS serving music files to my Sonos box doesn't need any security. And, my music appliances really want to mount SMB shares instead of AFP.
Oh, well... I am pessimistic that anything will get fixed.
