Acronis ExtremeZ-IP Seamless Integration of Macs into Windows Infrastructure

Mavericks File Sharing Tips & Reports

OS X 10.9 SMB file sharing with Windows and NAS devices

On this page:

Mavericks problems with some file servers

Readers are reporting that they cannot connect to certain file servers and network attached storage (NAS) devices after updating their Macs to OS X 10.9. Mavericks is backwards compatible with all file sharing devices, according to Apple, though it now defaults to the new SMB 2 file sharing protocol. The older CIFS/SMB and AFP protocols are still supported (contrary to what some of the tech sites have reported).

Reports from readers indicate that Mavericks may not be switching to SMB or AFP when a device doesn't support SMB2. It's also possible that Apple's implementation of SMB2 is not compatible with certain devices.

Ron Wilfred has a problem connecting to Windows:

After upgrading my MacBook Pro (2011) to Mavericks, I can no longer connect to my Windows 8 PC for file sharing. It worked perfectly before, but now won't now. I can still connect to the PC from an iMac with Lion.

Garth Bell can connect to his NAS device but can't open files:

I have an iMac that I upgraded with Mavericks. Whenever I connect to a Netgear ReadyNAS from the Finder, it won't let me open files. When I double-click a file I get an Error -36 message saying it can't open the file. I can copy files from the NAS to my Mac and back again as a workaround, but this is a pain.

Jeffery loses a connection after sleep:

Mavericks has made connections to my NAS drive temporary. When my Mac goes to sleep, the drive is gone. I can bring it back after a restart. This is annoying enough to make me want to go back to Mountain Lion.

If you've seen a problem with Mavericks and files sharing .

TIP: Force SMB1 as workaround to Mavericks file sharing

Several readers offered a suggestion for yesterday's report of problems with OS X 10.9 Mavericks accessing some Windows file servers and network attached storage device. Mavericks now defaults to SMB2 file sharing protocol, but a bug seems prevent OS X from using SMB1 or AFP when the server doesn't support the newer SMB2.

A workaround is to force OS X to use the old SMB1 (also known as SMB/CIFS). To do that, instead of mounting the server using the Finder, use the Connect to Server command in the Finder's Go menu. Then type in the following:

cifs://server_address (using the IP address or network name of the server)

Using smb://server_address won't work, as this will use SMB2 to access the device.

Thanks to Mario Cajina and Kevin Lepard for the suggestion.

If you've tried this workaround .

TIP: Using CIFS speeds Mavericks filesharing

Bill Haynes said that the reported workaround for broken filesharing in Marvericks not only works, but speeds up moving files and sending attachments via Mail through Exchange Sever. Haynes reports:

Wow! Changing my server mount to the cifs prefix resulted in a huge speed gain. I run AutoCAD Architecture 2012 in Parallels 9. Loading and saving to the windows server and the updating of external references had really slowed down to a crawl after I upgraded to Mavericks.

Also, adding attachments in Mail and sending is now much faster. Our Windows server is also our Exchange server. I have been having problems getting Mail to send when I attached files from the server. Instead the message would just hang in the outbox.

Does the cifs workaround speed up your filesharing?

Mavericks file sharing disconnects even with SMB1

Adam Elliott reports that OS X Mavericks disconnects on multiple Macs even when using SMB1 instead of the default SMB2 We've previously reported a workaround of typing CIFS:// in Connect to Server instead of using the Finder to connect to the server. This is a workaround for being unable to connect.…(Read entire story here.)

Mavericks file sharing workaround a no-go for reader

Reid Douglas reports that a previously reported workaround for Mavericks file sharing problems doesn't work for him. OS X 10.9.1 still won't mount his Buffalo Tech network attached storage device:

I've read several times about the Finder>Go>Connect to Server solution for NAS connectivity problem. I have Mavericks 10.9.1 on my iMac and have tried this approach several times using both cifs://server_name and cifs://server_IP and have never been able to connect to my Buffalo Tech HD-HGLAN drive. The Buffalo NASNavigator2 software properly identifies the drive by name, Workgroup, IP address, etc., and properly shows the available space on the drive. I can connect to it through the Buffalo setup software well enough to format the drive and set up a Mac share, but I cannot get it to mount.

If you've seen this problem .

Reader says SMB works, CIFS doesn't for Mavericks file sharing

Hugh Lancaster found that a workaround for Mavericks file sharing problem didn't work. The workaround is to force OS X to use SMB1 by typing cifs://server in the Connect to Server dialog. But oddly, Lancaster can connect with smb://server instead, though not with the Finder:

I have the same problem. If I connect over Ethernet I can "Connect to Server" smb://servername I am successful. If I connect via wireless, sometimes I can connect sometimes I can't. I tried cifs://servername but no success.

Earlier this week, another reader reported that the workaround didn't work for him, either.

TIP: Possible workaround on Mavericks file sharing disconnects

Adam Elliott updated his report from yesterday by reporting some success with his problem of Macs with OS X Mavericks disconnecting from Windows Server. He did this on the Windows server by enabling then disabling TCP Chimney Offload and Receive Side Scaling (RSS), features designed to increase…(Read entire story here.)

Mavericks changing permissions of SMB server

Florent B. reports an odd problem with a Mavericks client on Active Directory changing the permissions of an SMB server. When viewing a mounted share from OS X's Info window, the server removed permissions from all groups. Other users on a Google group he posted to confirmed and offered fixes.

Florent wrote to us about it:

I noticed your post about SMB and Mavericks, your readers may be interested by this crazy bug I published on the MacEnterprise forum. Some reported that creating new files on the server caused the issue. Florent was accessing a network attached storage device, but others report similar issues with Windows Server, all on Active Directory. One user found the problem using the Centrify Active Directory system and also with the Apple AD plug-in.

It was suggested that problem occurs when a share permission is set to "Everyone = Full Access," and that changing this to "Everyone = Modify" prevents the problem.

If you've seen this problem or tried the suggestion .

More Mavericks file sharing problems: DFS, zip files, and Indesign

Christoph Sternberg has the problem described in "Mavericks file sharing disconnects even with SMB1," but on a non-Windows server. He's also seeing a problem with DFS, with zip files residing on the server, and with Adobe InDesign files… (Read entire story here.)

Mavericks corrupting InDesign files on Windows servers

Shane Hughes wrote in response to a report on Monday about problems with Mavericks and Adobe InDesign on Windows Server, which caused the reader to downgrade to Mountain Lion. An earlier report described that the server was disconnecting. Hughes' problem is the InDesign files are corrupting… (Read entire story here.)

InDesign problem with file servers seen with Mountain Lion

Dan Ball responded to yesterday's report about Mavericks corrupting InDesign files on Windows servers:

I have problems with InDesign CS6 with 10.8.5 corrupting all the time with our students. I think the problem is InDesign! Even copying the files locally sometimes and working on them I see InDesign have issues.

If you've seen this problem or have a suggestion .

More on Mavericks InDesign corruption and SMB nsmb.conf

Anthony Godwin provided some new information about the previously reported Mavericks problem saving InDesign files on file servers, although his files aren't corrupting as others have reported. He has also reports success with the previously reported workaround for Mavericks SMB file sharing problems …(Read entire story here.)

File copy error -36 reported with 10.9.2 and OS X Server

Mac uses are reporting that updating Mavericks to OS X 10.9.2 results in a new file sharing problem connecting to Mavericks Server. Posts at the Apple discussion forums are reporting a -36 error when trying to copy a file to the server after updating the client to Mavericks OS X 10.9.2. A workaround… (Read entire story here.)

More on OS X Server 10.9.2 error -36 and new iMessage problem

Paul Roderer's Macs are having the previously reported problem of not being able to copy files to OS X Server using SMB after updating the server to OS X 10.9.2 and Server 3.0.2. He also discovered that the Server-hosed iMessage service no longer works after the update: We're getting Error 36… (Read entire story here.)

Turning off SMB for OS X Server 36 error, and DS_store files

Timon Royer is another reader experiencing -36 errors when Macs try to access Mavericks Server using SMB. Responding to our suggestion to turn off SMB to force Macs to connect with AFP, Royer points out a need to turn off SMB on the server in two different places. He also wonders if his IPv6 configuration… (Read entire story here.)

TIP: Two workarounds to Mavericks -36 errors, nsmb.conf and POSIX permissions

Jochen Lannig sent us two different workarounds to the problem of - 36 errors with Mavericks 10.9.2 copying files to OS X Server 3.0.2. The first involves creating or editing an nsmb.conf file to force the use of the SMB1 protocol. The second is to use only POSIX permissions (not ACLs) to share… (Read entire story here.)

Mavericks error -36 problem seen with Server 3.1.1

Steve Knattress wrote that the previously reported problem of -36 file sharing errors with OS X Mavericks Server also occurs with Server version 3.1.1. He can copy files one at a time, get the error, and then copy another file. Knattress didn't mention if he tried the workarounds we've previously… (Read entire story here.)

Reader says OS X 10.9.2 update still can't connect to NAS

Paul Du Vé reports that the Mavericks 10.9.2 update did not help with his inability to connect to a network attached storage device. The previously reported workaround of forcing a connection to SMB1 (rather than the default SMB2) didn't work. Du Ve writes: For me the inaccessible NAS issue continues.… (Read entire story here.)

Reader reports slow MS DFS access with Mavericks

Gert Goos is having a problem with slow OS X Mavericks connections to Microsoft Distributed File System (DFS) servers:

With DFS we have another problem: Since Mavericks, it is very slow until the folders under the DFS links are shown in Finder. This happens when many users are active. Inside the folders all works fast as expected. Mostly you have to switch between several DFS-links until the content of the wanted link is shown.

If you've seen this problem or have a suggestion .

Mavericks, InDesign issue with 2nd display

Tina from Denmark wrote to describe a problem she was having accessing InDesign files on a server after updating her Mac to OS X Mavericks. When she disconnected her second monitor, the problem disappeared. She writes: I have big problems with my Adobe InDesign and Mavericks. I downloaded Mavericks… (Read entire story here.)

Mavericks breaks ACLs in Active Directory, 10.9.2 made it worse

Jared Hendrickson reports that OS X 10.9.2 made file sharing worse on his Active Directory network. Mavericks bound to Active Directory broke ACL permissions when the permissions are viewed from the Mac. (Apple acknowledges this in a tech article.) Hendrickson found a workaround, but it stopped working with 10.9.2. The update also prevented Windows users from accessing folders that had permissions altered. His only workaround now is to unbind the Macs from Active Directory. Here is Hendrickson 's report: (Read entire story here.)

TIP: Workaround for Mavericks ACL permission bug

Jared Hendrickson followed up his report from yesterday about Mavericks breaking ACL permissions of shared folders in Active Directory. Unbinding the Macs from Active Directory was the only way to prevent corruptions of permission. Today, he reports a new workaround that allows the Macs remain bound… (Read entire story here.)