“Apple’s OS X Mavericks rollout, though not perfect, has been pretty darned smooth,” FairerPlatform reports. “Of the relatively few issues that pop up repeatedly, the Mavericks SMB2 connection problem is perhaps the most vexing. Although there isn’t fix yet, there are workarounds.”
“The issue likely stems from the fact that Apple has made major changes to how computers connect to each other in OS X 10.9. Specifically, with Mavericks, Apple is transitioning away from the AFS (Apple Filing System) and SMB1 protocols in favor of the SMB2 standard used in Windows and Linux,” FairerPlatform reports. “Yes, AFS and SMB1 are both still in Apple’s network stack, for compatibility with older machines, but SMB2 is now the default.”
FairerPlatform reports, “Again, although there isn’t a fix yet available for these problems, Michael Larsen has written up the issue, as well as a work around.”
Full article here.
“Apple’s SMB2 implementation is not compatible with many other SMB2 NAS products on the market today while Windows 7, 8, and 8.1 works just fine. In short, its an Apple bug.”
On the contrary, I would bet that as usual, Apple has written its application to the original industry standard, while as usual, other have introduced proprietary changes that are not part of the industry standard. Microsoft is known for doing so simply to make competitors incompatible. That’s called abuse of a monopoly.
I’m not sure where I stand as I’m lacking the inside knowledge of the protocol as well as first-hand experience with this. You’re right that Apple does try to adhere to standards that are accepted rather than define their own (IMAP vs. MAPI, vCard vs. the others, XML for plists, etc.), but there are still many areas where they remain proprietary and incompatible. For example, their office suite documents can’t be opened by anything excep their office suite, and apparently they dropped RTF exporting from Pages? WTF!?! So the jury is still out there for me.
The cheeky comeback would be: Since you can edit Pages documents on ANY machine with a browser, why would you need RTF? 😛
The pragmatic comeback would be: you can edit Pages
documents on ANY machine with a browser as long as
ANY machine can access the internet under ideal conditions.
It’s obvious you don’t know, Zeke, but thanks for the speculative hypothesis.
Your 2nd part is possible however I wiresharked the problems between OSX Mavericks and Windows 2012 Server. It is working fine with small files. When large files come in (GB’s) then the problems are coming. The logging tells “Len adjusted” “Must be low on credits”. Keep in mind that SMB2 is much more advanced then SMB2. A lot of things are exchanged much more then just transferring files. Reauthentication | Encryption | Streams | File Allocation | Record Locking etc.
The fixes which you can read everywhere are skipping one part. SMB is much slower. It sticks at 60 – 65MBs max while SMB2 takes the full bandwidth.
ever since i installed mavericks, my mac won’t shut down. it looks like it shuts down, but then after a couple of mins it come back on and the gray screen says, in multiple languages, that there was a problem computer was restarted.
can’t figure out how to get out of this, except to hold down the power button on back of mac
That’s a “kernel panic” and usually indicates some kind of a hardware problem. There are logs on the Mac that explain why the Mac crashed. (Mind you, I’m not qualified to read them.)
——RM
My father had this problem with Mt Lion on a mini, multiple trips to the Apple Store, replacement hard drives. Then he
swapped out the Samsung monitor for a Sony. Works fine.
It was the gimpy HDMI ports in that case; don’t know how you connect? Is it an iMac?
no, this is a mac mini connected to a vizio hdtv. only started having problems after installing mavericks. i’ll check the hdmi cable
I use AFP at work to connect my Mac Pro with our Windoze servers. I am using Mavericks so no issue there. SMB doesn’t work with Mavericks for me.
What AFP server are you running on your windows servers?
SMB has always been buggy from SNow Leopard upwards and Mavericks doesn’t seem to like MacServerIP AFP shares..
Adobe Photoshop crashes with “Program Error.” Adobe Illustrator says “not enough memory to open files” Adobe InDesign opens but refuses to create files.
and this has exactly what to do with SMB2?
I can go even further afield of the topic and rue that they
didn’t call it Sea Lion and charge $9.99 for it. Whittle it
down to free, don’t just go from $20 (which is still good)
to “free”. It raises a spectre: didn’t the bakery down the
street give away that free bread and later we learned
wheat deliveries were missed but somehow all the empty
cardboard boxes didn’t need to be hauled away?
The funny thing is before I used to have connection to winblows problems, but now it seems to connect very easily. I don’t know if I should be happy or scared.
There is no such thing as AFS (Apple Filing System). The author likely means AFP (Apple Filing Protocol). No excuse for getting that wrong, it’s a tech article and acronyms should be accurate.
So… if I upgrade my Mac mini (running Mtn Lion) to Mavericks, does this mean I am more likely to have problems directly connecting to my living room mini running Snow Leopard? I use file sharing to transfer files between them quite often, and have had an occasional connection problem between Macs running the same OS version (Snow).
The living room mini is a home theater PC used by my wife. We use Front Row, so it’s not getting updated anytime soon. Also, the wife wouldn’t be happy with ANY consequential glitches.
And…. speaking of home theater Macs, does anyone know why you can’t find any ElGato EyeTV Hybrid hardware in the U.S. … or anything similar for Macs? The latest info I could find is about two months old and doesn’t even address why. It’s just a thread post in a MacRumors forum by someone making the same inquiry and didn’t generate any real answers.
Wonder if/how this is going to affect render farms using Qmaster and the new compressor on multiple machines?
I have also seen this issue with drives that are setup as NTFS folders on a Windows file share. You can connect to the file share, but when you get to the drive that is shared as an NTFS folder it shows up blank. But if you know the folder you want to go to in that share folder you can get to it, but mapped drives to those folders show up as question marks. What I’m talking about with drives mounted as NTFS Folder: http://www.howtogeek.com/98195/
Would MAPI2 be responsible for changing the file extension if the system doesn’t know or recognize the extension what the extension is?