Strange thing keeps happening with one of my clients. They are running 3 iMacs 2of which are running 10.9.3 and 1 is running 10.9.4. While they are accessing a Windows share, they can be working away quite happily until it comes to saving where they no longer have access to the file opened from the server and have to save as a new file. They are accessing using smb://{servername}/{share}

What would cause this?



Apple moved to SMB2 in Mavericks. There have been many reported issues regarding Macs using SMB2 to access Windows shares. There's even a site dedicated to this specific set of issues!

For a dated, but good explanation of work-arounds see this ZDNet article.


Have your users try cifs:// instead of smb:// (assuming your Windows share supports CIFS)...and hope that 10.9.4 comes with an SMB2 fix. :)

  • Thanks for the reply @thankyour. I haven't tried cifs:// yet. The strange thing is that I have another client which is using a Mac Server running 10.8.4 with clients running Leopard, Snow Leopard, Lion, Mountain Lion and Mavericks, all using afp:// and have similar issues. I know there are issues when it comes to Adobe as they say it is not designed to work from a network share, but it also has the same issues with Word, Excel, Pages and others aswell – bassdude1986 Aug 14 '14 at 8:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .