Tuesday, October 22, 2013

OS X 10.9 Mavericks Workaround for SMB

Upgrading is never easy.  There is always some new bug introduced as a feature.  That said, you may have noticed that connecting to NAS shares worked perfectly in OS X 10.8.x but doesn't anymore in OS X 10.9 (Mavericks).   Here's the lowdown:

DISCLAIMER:  Though these are pretty harmless changes, any changes you make are at your own risk. 

Issue: 

Clients logging into File Services over SMB with OS X 10.9 experience hanging connection upon login attempt.

Root Cause:

OS X 10.9 now utilizes a new SMB2 stack written by Apple.   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.

Workaround Option 1:

To force your connection to be SMB1, simply type cifs://servername instead of smb://servername when connecting to a Windows or NAS share.  This is by far easier and requires no real configuration changes.

Workaround Option 2:

To force all connections to be SMB1:
  1. Open A terminal window
  2. paste in the following line followed by the return key(should be all on one line):  
echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf

What the command does:
  1. Creates a file called nsmb.conf  in your  home directory at the path ~/Library/Preferences/nsmb.conf.
  2. Adds directives to force SMB connections to use the SMB1 protocol.  This is slower but stable.

How to remove the workaround:
  1. Open a terminal window
  2. paste in the following at the prompt and then hit the return button:
rm ~/Library/Preferences/nsmb.conf

Notes:

Its a good idea to restart your mac before trying to connect to your storage again. This will clear any hung SMB processes from previous attempts to connect to your storage before implementing this workaround.

94 comments:

  1. Thanks a lot! Solved our problem connecting to the university share.

    ReplyDelete
  2. Any idea if this issue is part of this problem?

    https://discussions.apple.com/message/23478758#23478758

    ReplyDelete
    Replies
    1. Yes it does seem related. Using cifs:// makes a connection to an SMB share using SMB1 instead of SMB2. Seems like there are a number of issues with SMB2 not just the initial connection.

      Delete
  3. Option 1 was perfect, thanks for sharing

    ReplyDelete
  4. Option 2 makes me happy, thank you!

    ReplyDelete
  5. i've tried your command, but nothing happens, i've went to preferences folder and it didn't created the .conf file... should i check for something else?

    ReplyDelete
    Replies
    1. Sometimes cut and paste doesn't work properly. You may want to open a terminal session and type in the line manually. Just make sure you follow it exactly as far as when spaces are used and not used. Also you can quickly check from the command line if the file has been created by using the following command at the terminal:

      cat ~/Library/Preferences/nsmb.conf

      You should see the following as output if it has been created properly:

      [default]
      smb_neg=smb1_only

      Delete
  6. The problem with failing SMB connections is also true the other way round: connecting from a device (e.g. an iPad app or a linux PC) to the Mac via SMB. Does the above solution #2 also force INCOMING SMB connections to fall back to SMB1? Anyway: thanks alot for the hint!!!

    ReplyDelete
    Replies
    1. Unfortunately I don't think so. The conf file adjustment is specific to the SMB client within OS X Mavericks as far as I understand it. I have not tested whether this affects the OS X file sharing daemon, but some folks have commented that it doesn't work for them in regard to OS X sharing out files. I spent some time digging though some developer info this weekend but didn't see anything specific to address forcing SMB1 mode for OS X mavericks file serving. I'm pretty sure it supports SMB1, but you will likely have to force your client to connect SMB1 instead of expecting the SMB server/service part to force SMB1 connections.

      Delete
    2. As mentioned, the workaround that I provided above was intended specifically to affect your client. However, after reading the man page for nsmb.conf, its less clear to me if this affects only the client or may also affect the file service daemon. There is a global version of the nsmb.conf that can be stored in /etc. You could try creating an nsmb.conf file in /etc with the same directives. The file should just have these two lines:

      [default]
      smb_neg=smb1_only

      I'd be curious if this actually works. I know a number of folks are looking for a solution to serving files from OS X with Mavericks.

      Delete
    3. Mavericks (here: 10.9.2) indeeds supports SMB1 to share files. I had terribly problems connecting from my Windows 7 client to a Mavericks SMB share.

      As you said, forcing SMB1 on the client side is something that is not really recommended – but it works: I was able to disable SMB2 / SMB3 on the Windows box. See the following article: http://support.microsoft.com/kb/2696547

      Delete
    4. There should be some way to force Mavericks to rejecting SMB2 connect requests so that a potential client would then try to fall back to SMB1. The usual way would be something like /etc/smb.conf – which, as a matter of fact, does not exist on my Mavericks machine anymore after the upgrade, just an old /etc/smb.conf.old. Some say it's supposed to be in /private/etc/ – but same here: not smb.conf, just smb.conf.old. *headscratch*

      Delete
  7. My hero, this stopped me in my tracks this morning.

    ReplyDelete
  8. I've tried everything, it doesn't seem to work with our network. I even typed it in and it doesn't seem to take.

    ReplyDelete
    Replies
    1. Did it work for you before in OS X 10.8.x before the upgrade? The workaround on this page basically makes your SMB client connect like 10.8 did.

      Delete
    2. ok this is strange, I have several machines running 10.8.3 to 10.8.5 and some can do smb to the windows share link provided and some need the IP address to see the share. 10.9 WILL NOT see either... don't upgrade.

      Delete
    3. I'm hoping Apple will patch SMB really soon. Clearly a lot of issues need to be addressed in regard to SMB2 compatibility. As for the workaround not working, you really should validate that not only the nsmb.conf file exists but that the proper directives are in the file. (see some of my responses above about what that should look like) Without the directives the file is useless. OS X 10.8.x used SMB1 exclusively. All this workaround does is force your client connection to connect to the storage SMB1.

      Delete
  9. Doesn't work for me either - tried them all, the cifs in the Finder "go to server", the ~/Library/Preferences/nsmb.conf and the /etc/nsmb.conf. It was working with 10.8.x and I didn't touch the configuration of the router. Point is, I don't see any log file I can start from to understand what is going on.

    ReplyDelete
    Replies
    1. I'm curious what NAS or file server you are trying to connect to? (i.e., is it Windows 2008, etc) I'd like to see if there is a correlation to some storages that don't work even with the workaround. If cifs:// and the other option don't fix the issue, it could mean a couple of things. 1) That your SMB server you are connecting to is not supporting SMB1 2) There may even be a further incompatibility between SMB1 and the storage you are trying to connect to.

      Delete
    2. Also won't work as cifs. Haven't tried option 2 yet. Our server is a Windows 2008 R2.

      Delete
    3. Just to add that I solved the issue and I am now able to connect to the NAS with the cifs command. The point being I need to include the sharename so, in Finder -> Go Server I use

      cifs://192.168.1.1/discosusb

      for the spanish Orange LiveBox router. And it works. To discover the name of the shares, I went back to use Mountain Lion on a virtual machine (virtualbox) that was connecting fine. It seems that it works also with the smb command, but it is way slower than cifs.

      Delete
  10. Yea, for me, I could connect to our Windows 2003 domains and rename files but could not copy files from my Mac to the drives. It seemed to work but I would drag and drop and got no error but the file would not show up at the destination. I changed the connection to cifs: and things are working now.

    ReplyDelete
  11. Doesn't work for me. Two servers with WS2008, one connects file, other doesn't. No problems whatsoever with 10.8.

    ReplyDelete
  12. Thanks for sharing. That worked for us.

    ReplyDelete
  13. Thanks for the post. I tried Option 2 but my Mac with 10.9 is not working with my Synology NAS via time machine. It is taking 15 hours to back up less than 1GB. When I connect to my NAS I see that the connection is AFP. Can you provide me any guidance? Before Mavericks this all worked perfectly. Any/all help is appreciated!!!!

    Thanks
    Ray

    ReplyDelete
    Replies
    1. I figured this out. I had an incompatable version of Norton installed which caused my whole mess. I uninstalled it and all is working fine. Downloaded the upgrade from Norton and all is working.

      Delete
  14. Hey Michael!

    your instructions are awesome and the best I have found on this subject.

    here's my predicament: I print from a Mac to a virtual printer (basically a shared printer) which runs on Windows NT4 which runs Onyx RIP software to print to a large-format HP DesignJet Z6100
    everything works using smb://servername/printername but once upgraded to Maverick I get an error message in the printer queue "Unable to connect to printer". I have deleted the printer, followed your instructions and I verified the nsmb.conf file lands in the proper spot (and it does). after a reboot I add the printer using the exact same method, but the error stays the same.
    I'm able to Connect To: using either smb or cifs. I am however not able to Add a printer using the path preceded by cifs, the Add button stays grayed out.
    any suggestions other than going back to Mountain Lion for now?

    thanks!

    ReplyDelete
  15. I have a "smb not supported" problem having upgraded to OS X Mavericks from Lion. I'm trying to connect to smb servers but just get the error message "There was a problem connecting to the server. URLs with the type "smb:" are not supported".

    I have read and tried the 2 workarounds on here -

    1 - The CIFs workaround gives me "There was a problem connecting to the server. URLs with the type "cifs:" are not supported".

    2 - The terminal nsmb.conf file workaround results with the same "URLs with the type "smb:" are not supported" message.

    The AFP alternative does not work - I get: "There was a problem connecting to the server "servername". The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again."

    Does anyone have any other suggestions... Are Apple working on an update for this problem? When can we expect a fix?

    ReplyDelete
  16. What NAS are you using? Looking at packet captures in an effort to figure this out I saw that some Synology NAS devices violate the SMB 2 specification. http://msdn.microsoft.com/en-us/library/hh554066.aspx

    Specifically they respond to the client request for SMB 2 negotiation with a version specific "SMB 2.1" string rather than the required "SMB 2.???". It seems like the Apple client is coded to the specification so things fall apart at that point as the server doesn't understand the next message.

    Looking at every Windows server I can find they all reply with the proper "SMB 2.???" reply, but also Windows clients will accept a broken server negotiation as well.

    ReplyDelete
  17. Hi macshome - thanks for the response - it turned out that it was an installation of Thursby software ADmitMac v6 on my system that was creating a conflict. Smb is now working fine following a deinstallation - if anyone else is struggling:

    To remove ADmitMac, use the following uninstall utility:
    /Library/Application Support/ADmitMac/Uninstall ADmitMac

    It turns out this software is not compatible with OS X Mavericks: http://www.thursby.com/known-admitmac-issue-cannot-log-after-upgrading-mavericks.html

    ReplyDelete
  18. My command is : smb://(ServerIp)/(sharename) , This was connecting but very slow response. I tried cifs://(ServerIp)/(sharename) this is little better. I need day or two to tell the exact feed back.. Thanks for this update. BTW why apple use such a critical protocol to connect network shares.. hope they will fix this problem in next update!!

    ReplyDelete
  19. I work on copiers and we have customers that want to scan to a shared folder to mac 10.8 and 10.9 via SMB (im guessing SMB1 from copier) we get stuck at the point where you select a shared folder. Copier tells us there is no connection to mac. Will any of these help connection from any major multi function copiers? (ie Canon ADV 6055)

    ReplyDelete
  20. Is there a Mac solution for the MoveSecurityAttributes registry adjustment on windows platform to change default move permission handling in same NTFS volumes?

    ReplyDelete
  21. Thank you for sharing this article!! I was confused and STUCK after update to 10.9!! Simply by pasting your line to Terminal now my problem is SOLVED :D
    By the way, the First soultion didnt work for me.. But the Second worked like a Charm.
    (I still wonder why Apple do this SHIT, that was breath taking.. Had even to Pay for OSX Server once more cause this STUPID UPDATE)


    Thank a million for your help, and a Great solution!

    ReplyDelete
  22. Hi,

    Thanks for sharing this article.
    Somehow i am not managing to get this working...

    I have to connect to a https over the internet

    both the cifs:// etc solution and the ~/Library/Preferences/nsmb.conf solution did nothing for me.

    It dit work before my upgrade to mavericks though.
    Any suggestions?

    ReplyDelete
    Replies
    1. Creating the file doesn't do anything until after a reboot.

      Delete
  23. 10.9.1 seems to have broken SMB connection again. Any workarounds for this latest update?

    ReplyDelete
    Replies
    1. Doesn't seem that 10.9.2 resolved anything for me. At this point, the workaround still works for me, but it is dependent also upon the storage you are connected to.

      Delete
  24. This comment has been removed by the author.

    ReplyDelete
  25. Hello, Neither of them work for me. It says me "Server Version your are trying to connect is not compatible. Keep in contact with your administrator...." I'm trying to connect a Spanish LiveBox router (Orange company) to my MacBook Pro.

    Is there any command to restart my SMB configuration and try your solution again?

    Thank you

    ReplyDelete
    Replies
    1. Sounds like the storage you are trying to access doesn't support SMB1. In that case you are out of luck unless updating your Spanish LiveBox helps resolve it.

      Delete
  26. Great workarounds.

    Now... can anyone help me bind a Mavericks machine to Active Directory?

    ReplyDelete
  27. Tried options and not working for me. I'm connecting to a SMB share through another device. This worked great in 10.8. Funny thing is connecting wirelessly and transferring (although slow) goes faster than hardwired. Odd..

    ReplyDelete
  28. When using SMB1 it's no longer displayed in the backup volumes of Time Machine, is that right?

    And workaround to get Time Machine Backups working with this workaround?

    ReplyDelete
  29. Also found this article: http://apple.stackexchange.com/questions/107032/time-machine-backup-to-an-smb-share-mavericks

    Result from tmutil is:
    Incompatible file system type: smbfs (error 45)

    ReplyDelete
  30. YES! Was trying to connect to files on a shared drive attached to a Mac Pro with no luck, managed to fix the permissions on the external drive and allow myself access then had issues with files only on the drive...Photoshop ICC errors and Illustrator freezing. Thank YOU! The workaround #2 worked perfectly.

    ReplyDelete
  31. Thank you for that workaround. I just upgraded from Snow Leopard to Mavericks and I am having the following problem with my NAS (Raidsonic IcyBox NAS3221-B): I can connect using cifs and smb (even without your workaround) and I can see the content of the user-folder. But from here all other folders are forbidden and I can't open anything. Unfortunately your workaround has no effect here. Do you have another idea?

    ReplyDelete
    Replies
    1. I'd check to see if there are any updates for your Raidsonic IcyBox. Just as updating your Mac is important, so is keeping up with firmware/OS on your home NAS.

      Delete
  32. I don't know if my problem is related or not. I can access my shared drives and NAS when connected to the network wired but not through wifi on the same network. I've tried cifs and smb with no luck. What am I missing here? Prior to Mavericks this was not a problem! Eeek!

    ReplyDelete
    Replies
    1. First, I'd check to make absolutely sure they are on the same network. The fact that both wired and wireless can access the internet doesn't guarantee they are on the same network. Some routers separate wifi traffic out from your local LAN traffic like in the case of a "guest" network. This is done as a security feature to allow your visitors to access the internet but not get access to your home network.

      Delete
  33. option 1 was perfect for my nas (iomega home mdeia CE)

    ReplyDelete

  34. Hi Michael,

    I am also seeing issues with my SMB2. I am trying to connect to a WD Tv Live Hub. I have tried to change the SMB to the CIFS but I am still not able to connect the mac to the WD. Any advice? I am trying to get the WD to show up under shared devices so I can drop videos and pictures to the WD (which is on my network). Any ideas...(I have not tried Option 2, I am a novice and dont want to screw my computer up lol.)

    (command + k) I entered these in to the server address name...

    Original
    smb://wdtvlivehub

    To
    cifs://wdtvlivehub

    Showed an error that my mac wasn't able to read the WD.

    Thanks in advance for any help!

    ReplyDelete
    Replies
    1. The only other option I could suggest would be check with WD and see if there are any updates for your TV Live Hub.

      Delete
  35. The CIFS option had been working for me, but no longer does. Both the Windows PC and Mac are fully patched. Not sure, but maybe one of the improvements has broken the ability to connect to a share again.

    ReplyDelete
  36. Hi Michael,

    Thanks for the workaround. It almost works for me, but not quite - when I follow option 2 and restart my Mac, I can connect to my personal network drive but on subsequent days, it's back to not working again. If I clear out the nsmb file and start again, it works - but again only for that day.

    Any insight would be appreciated, thanks.

    ReplyDelete
    Replies
    1. Hmm, that's an interesting issue. It almost sounds more like a possible firewall or network issue. Check for virus/firewall software on either your Mac or if you are connecting to a PC, on the PC side. Clearly the protocol works, it seems to me to be some other factor interfering. Seems less to be about a SMB1 or 2 which is what the workaround was designed for.

      Delete
  37. This doesn't work for me - on 10.9.1 Mid 2012 15" rMBP.

    ReplyDelete
    Replies
    1. It is likely that the system you are connecting to either doesn't support SMB1 or does not have SMB1 enabled. Otherwise the above should work for you. As for the default SMB2 on 10.9.x, clearly there seem to be continual reports of issues with it.

      Delete
  38. Hello All,

    Ran into this blog and decided to post my scenario. I have a Mac Mini running Mavericks 10.9.2 on a wired network with a Vista Ultimate and an XP machine. I can connect to the Mac Mini shared drives from both the Vista and XP computers. I can connect to the shared drives of the XP from the Mac, but I cannot connect to the shared drives on the Vista from the Mac. I implemented both fixes suggested and none have worked. Crazy thing is, if I run XBMC from the Mac I can access the shared drives on the Vista computer... Any suggestions would be greatly appreciated.

    ReplyDelete
    Replies
    1. Vista implemented a newer version of SMB than that in XP. That would explain the difference in compatibility. Though I don't have a specific link to provided, there are likely some options to adjust your Vista machine to allow SMB1 connections from your Mac. Its likely that Vista is expecting SMB2 connections and may not allow SMB1 connections.

      Delete
  39. Thanks a bunch. I had this problem from very long time.

    ReplyDelete
  40. Michael,
    I have three Mavericks computers on 10.9.2 that are having connection issues with an EMC VNX NAS. Currently they all use CIFS to connect and none of the computers have been joined to the Domain. They would like to use SMB so that they can Tag files/folders. This cannot be done in CIFS. Also, they are seeing permission issues when trying to rename/move files/folders. Do you have any suggestions that might be able to help me out?

    ReplyDelete
    Replies
    1. Have you tried my second solution (the one that creates a conf file) on the Mavericks computers? You will have to reboot after applying it in order for it to work. The workaround won't work for you if either the VNX doesn't support SMB1, or there is some incompatibility between Mavericks SMB client and the VNX. In such a case, I'd recommend researching the current OS/Firmware level of the VNX to see if you are at the latest version. If there are new versions of the VNX OS/Firmware available with specific fixes for SMB, this may be the ticket. Before upgrading through I'd suggest working with your EMC account team to see if there are specific fixes that may allow it to work better with Mavericks.

      Delete
    2. I have not tried the second fix yet. Isn't using CIFS the same as applying the second fix anyway? Do you think we would gain anything by joining the computers to the domain? They connect to the server using their network username and passwords, so I am not really sure if it would help. I think I best answer might be to go to the EMC team and see about updating the firmware there if it is not up to date. I will keep you posted on any progress we make. Thanks for writing back so quickly.

      Delete
  41. I tried running the command above, but it does not look like it created the nsmb.conf file. I did both ways, cut and paste as well as typing it out. Am I missing something? Is there a different way to create this file without using that command...maybe create the file, then edit the file using the terminal window? If so, how would I go about doing that?
    Thanks again for your help.

    ReplyDelete
  42. I don't understand what you mean by "simply type cifs://servername instead of smb://servername when connecting to a Windows or NAS share" in workaround 1.
    When I am trying to connect to this, I am not typing anything, I am just clicking on the external harddrive and trying to click "connect as" but with no response.
    A little clarification would be great!

    ReplyDelete
    Replies
    1. I'm sorry - "external harddrive"? That can't be right. You're trying to connect to a network server, right?

      In that case, you'd usually see the name of the server in the lower right of your Finder window. If you would click it there and the click on "Connect as", OSX would usually try to connect via SMB.

      Instead, head for the menu and select "Go" / "Connect to Server" and enter the server's name manually. But instead of entering "smb://servername", please enter "cifs://servername".

      ... Hope that helps.

      Delete
  43. Thanks for the post Cammodude,
    Unfortunately none of the work arounds posted on the web have helped us at all with the issues (some of which we have documented here macsmbissues.com) we have been having since upgrading some of our clients to OSX 10.9.2, so we went back to 10.8.5
    Hope Apple is listening.

    ReplyDelete
  44. Fantastic blog!!! This blog helps you to solve your any knid of windows 7 firewall error , its can get instant service provider.go through this link.
    windows firewall error 1068 windows 7
    Thanks
    Aalia lyon

    ReplyDelete
  45. "To force your connection to be SMB1, simply type cifs://servername instead of smb://servername"

    Um, perhaps a newb question, but for the novice, type it where?

    ReplyDelete
    Replies
    1. Head for the menu in Finder, and select "Go" / "Connect to Server" and enter the server's name manually. But instead of entering "smb://servername", please enter "cifs://servername".

      Delete
  46. This problem plagued me for months till I found your solution. I have a WD Live Hub & a MBP running Mavericks. I used option 1 and it worked until yesterday. It just stopped working. I didn't change or upgrade anything that I'm aware of. Now option 1 nor option 2 works. This is so aggravating. I wish I could downgrade to Mointain lion.

    I noticed when I go to "more info" on the network drive it says server is SMB, even after typing in CIFS. Shouldn't it be CIFS server?

    ReplyDelete
  47. Tried option 2 with 3 different Boxee Box units. Couldn't get any of them to connect to a shared drive on 10.9.2. Ended up having to use SMBup. Curious though, but has anyone here with a Boxee gotten theirs to properly connect using option 2? All I get is a username/password loop.

    ReplyDelete
  48. The cifs:// doesn't work for me BUT I can connect to it using the muCommander app which is using the SMB protocol. Any ideas how I can mount the drive?

    ReplyDelete
  49. I have a Netgear ReadyNAS NVX and if I connect to the shares using cifs:// or smb:// or afp:// from a mac with 10.9.x It takes more than 4 hours to write 1GB to the share. Confirmed that connected to the same share from another mac on the network without 10.9 can write the same file in <1 minute to the same share. I have added the nsmb.conf file to prefs as listed here and in other forums, but neither that nor CIFS allows me to write to these shares in a usable fashion on 10.9. Any other thoughts? Anyone with a ReadyNAS on this ?

    ReplyDelete
    Replies
    1. I've got a ReadyNAS DUO and am experiencing similar issues... I'm on Mavericks 10.9.3 and can write to the NAS shares pretty quickly, but for some reason copying files *from* the NAS to my Macbook is incredibly slow. So, fast write, slow read?! Weird. I've tried both fixes in this post but neither have fixed this issue. I'm wondering if my issue is actually an smb issue as it's only copying from the NAS to the Macbook that appears to have issues (at least from what I've noticed so far anyway). Anyone got any ideas what the cause could be?

      Delete
  50. I have a mixed environment here of macs and windows and running Mavericks server for file sharing (using external Promise Thunderbolt array). Workaround 2 made sense to do on the server so that no user can connect via SMB2. It was successful so far and the volume dosen't become hidden after a day or 2 of usage as it was before. But now we can't connect via AFP which is needed for the HomeFolder sync and TimeMachine to work with the server. I need to know an option of disabling SMB2 only or to use either SMB + AFP.

    ReplyDelete
  51. Quite the lifesaver. My 10.9.x laptop hangs against Windows 8.1 (fully patched) and the SMB1 config (option 2) cures the problem. Nothing special on the 8.1 system other than it being MCE with cygwin also installed (for ssh). The share has global rw permissions for "everyone" so even guest accounts hung

    ReplyDelete
  52. Your solution works both ways. Now i again have a rocksolid filesharing system between my mac and pc. I can share both ways and with a higher speed now, than before with SMB2
    Thx this saved my day

    ReplyDelete
  53. I have newer Mac Mini, 16 Ram, SSDs, with 10.9.4. All same problems as noted here. I have Windows 2008 Server VM using Fusion working well that will map to host Mini shared drive and also map to the Mini's Pegasus with no issue. How is this possible? This is Windows to Mavericks and no SMB issue. Why does mapping on network v mapping to host differ? Worse, I've had added network problems not mentioned here killing further testing whenever I map to Pegasus from a Windows 7 Machine or map to Pegasus from XP machine after a time, maybe 4- 5 days. Network does not fail immediately. Very odd. Network slows down making it unusable after the workstation mapping begins to fail. After a time I cannot make use of Logmein as it became impossible and also Citrix failed. Today, I could not even upload a small PDF to google. This is a mess for me. I am testing the CIFS fix this weekend to see if my network functions as intended after mapping from Window 7 machine to Mini's Pegasus. What is causing the network slowdown? I miss 10.6.8 which was heaven compared to this debacle.

    ReplyDelete
  54. Great Job! I point people to this all the time.

    ReplyDelete
  55. Why, at first impression did Windows 7 mapping to Mavericks shared drive and the network seem to function via SMB and work fine only to fail after a few days? I think the failure began when I made an attempt to copy a backup drive of about 70 gig including a large image file to the Pegasus on the Mac Mini which then set off a chain of slowness events that became worse over time and finally got so bad as to be intolerable. It was after this large file copy event failure that I began to notice the dropping of the mapping from the Windows machine. Worse, something was still going on in the background to cause the network to fail. Only turning off the file sharing completely on the Marvicks Mini cured the network stability. I had tried to toggle the Maverick share on and off but that had no positive result on network slowness and only shutting off the share returned my network speed. This means I was fooled by initial connection seeming to work. Can anyone here comment on network slowdown and the cause?

    ReplyDelete
  56. If I limit my share to one Windows 7 Machine mapping as client to the Mavericks Mac Server shared Pegasus Drive the network has been stable for 5 days and no dropped connection. Tested heavy load file copy and it has worked so far but, it is slower than my ten year old Dell Server. Can anyone explain this? The speed is gone.

    ReplyDelete
  57. In my case it helped nothing at all :( I am searching the whole internet for a solution to get my time machine backup running on my Buffalo Link Station LS-QL/R5.

    Still gettin this Error "The network backup disk does not support the required AFP features."

    Any ideas?

    ReplyDelete
  58. Thanks man. This post saved my butt. This issue was areal head scratcher...

    ReplyDelete
  59. More headaches as my Second Copy Program I've used for at least 15 years can copy only once to Pegasus Drive and at very slow motion speed of over one hour when Window drive is less than ten minutes but now I can't recopy again he next day backup as now I get an error. This is more odd network behavior not experienced on OS 10.6.8., and certainly no other machines I've had. Something is radically wrong here with Mavericks and sharing with a Windows 7 workstation. But, oddly too, I can share perfectly with a Linux VM on the Host Mac Mini via Fusion using my Windows 7 workstation to map and all is well. I hope this helps someone get to the bottom of this an fix it. I too just began serious efforts on a Windows server and am also looking at Synology NAS. Still I wish Apple would fix this. I hate not using my new Mac Mini Server and Pegasus array the way I want.

    ReplyDelete
  60. Hello

    I have a ts809 raid 5 setup 4.1.0 build using mavericks. Using cisco cable modem and connect hard wired to the router.

    My transfer speeds are very wired, I did a test using speed test mini and I have results 94mbps up and 84 mbps down. But when I use another test disk speed test i get 11 mbps down and 11 mbps up. This is a big difference.

    When I unpack a big file 8GB is take 40 min to unpack from the NAS and back onto the nas. Using windows this was done much faster. Is there are issue here?

    Regards

    ReplyDelete
  61. Any one else experiencing slow network speeds after a time especially with file sharing and getting dropped shares when using Mavericks, and does anyone notice network protocols of their specific router and especially with use of Cisco routers impacting network speeds? Possible packets flooding network and irregularity? Does anything think there are two issues here? Samba and also network irregularity? There was no issue with my connection of Windows 2008 Server VM using Fusion using new Mac=mini- & Mavericks server as host with Server mapped to host shared Pegasus drive and upon connecting/mapping one more Windows 7 workstation to Pegasus drive things seem fine other than slower than normal network speeds. Add a 2nd XP workstation and network crashes within 3-5 days. This is very odd.

    ReplyDelete