(it turns out some users continue to have access issues with OS X Yosemite and OS X El Capitan, using CIFS continues to gain access to those windows shares and NAS volumes).

This really is just a bug with the newest version of Mac OS X, and it will probably be resolved shortly with an update to Mavericks, perhaps as OS X 10.9.1 or even a smaller supplemental update. With that said, going the other way around and file sharing from Mac OS X to Windows continues to work exactly as intended, though it should be noted that OS X Mavericks has seamlessly moved all network-based Mac-to-Mac file sharing to SMB2 as well, though the traditional AFP continues to function as well for legacy support and for connecting between Mavericks and earlier versions of OS X. Upload, download, and manage files on tons of servers with an. Because there are tons of Mac-to-PC networks out there, this will probably be a frequently encountered issue for many Mavericks users. The gold standard of macOS file transfer apps just drove into the future. I ran into this last night and it was fairly frustrating to experience, but a big thanks Todd Pilgrams on the Apple Discussion Boards who discovered the simple workaround a few days ago. The result cross-platform network shares functioning as usual. If you’re wondering why this works, it’s because using CIFS connects with SMB1 rather than the (currently) buggy implementation of SMB2. Yes it really is as simple as specifying the protocol to be cifs:// rather than smb://, which if you’ve ever mounted Samba shares from the command line you’ve probably already used cifs before. Connect to the SMB, NAS, or Windows share as usual.In the “Server Address” field, enter the IP to connect to with the cifs:// prefix as follows:.From the OS X Finder, hit Command+K to summon “Go To Server” as usual.

Smb client for android and mac os x