Can't connect to SMB share after upgrade

Hi Guys,

I'm using Maverick 10.9.2 and i'm not able to connect to any of the shared drive of my Win 7 or my Synology NAS from my MacMini. I've tried all the above fix but nothing seems to work, using afp, cifs nor smb. Also tried the one that creates the nsmb.conf.

When I tried to use the Connect To server in Finder using cifs, it asks me the username and password. And after entering them, it shows me the list of shared folders but when i click on any of them it says "There was a problem connecting to the Server..., You do not have permission to access this server." I have tried all the users available in the system including the admin but all fails.

Below is the error i get from the logs:

SDNetworkResolver::handleMountCallBack returned -50

When I access the Shared Folders in Finder, my mac mini can see my win7 pc and NAS server. It can even list the shared folders on each of them. But when I click on any of the shared folder it says "The operation can't be completed because the original item for ... can't be found."

Below is the error i get from the logs:

SDNetworkResolver::handleMountCallBack returned -50

dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7f9fcad415d0 FFFF0007 DDDDDDDD

I have spent a lot of nights troubleshooting this problem but until now have not found any workable solution.

Any of you having the same problem that I have?

slimfat wrote:

Hi Guys,

I'm using Maverick 10.9.2 and i'm not able to connect to any of the shared drive of my

... Synology NAS from my MacMini.

Have you applied the Synology fixes? What version of DSM are you using?

Yes I did applied them. Actually, at first I thought it was a synology issue. And i even asked synology support for assistance. But when my mac mini also cannot connect to my windows pc then I have isolated it to the mac mini configuration problem. My windows and my NAS have no issues connecting with each other.

I'm using DSM 4.3-3810 update 3. I just checked, there is a new version 5.0. Will try this out anyway.

Well, I have solved all of the issues that I had been previously experiencing with the XP machine and the attached external USB hard drives. The Mavericks machines were unable to connect to them and as I had reported earlier, I realized the problem was simply that the external hard drives, which were plugged into the XP machine via USB, were formatted in the Fat 32 format. Once I reformatted those hard drives in the NTFS format, all was working perfectly.

I have now recently discovered there is yet another issue that I have now realized is because of my most recent upgrade to Mavericks. Within our company's network, we have a Buffalo NAS TeraStation that is a gigabits NAS drive hooked up directly to our network switch. Every computer in our entire company can access this drive with no problem, Macintosh systems, PCs, all of the computers that we have been using are fine. With the exception of the two computers that we have just most recently upgraded to Mavericks. This includes a MacBook Pro, and a Mac mini. Both computers are exhibiting the exact same behavior. Simply, if we try to connect to the Buffalo NAS TeraStation on the network, instantly we are not even prompted with a connect as username and password option. We immediately get a message saying that the device that we are trying to connect to is not compatible. That is not the exact message but it is something to that effect. The Mavericks OS simply will not allow us to connect to these Buffalo NAS TeraStations. Now keep in mind, these systems run a proprietary UNIX file structure. I can't remember or recall the exact file structure name, but still the fact remains that all Mac systems, whether it's Leopard, Snow Leopard, even Tiger or Lion, or Mountain Lion, all connect the Buffalo NAS TeraStation with no problem at all. Of course the PCs can connect to them as well.

I contacted Buffalo and they suggested that simply I use the CIFS command within the finder's connect to server option. To no avail, this did not work. Interestingly though, the maverick systems do see the Buffalo system on the network, but I'm simply unable to connect to it. I updated the firmware on the buffalo terra station, and I was hoping that that would resolve the issue based on buffaloes own advice. But again it did not work. One other issue or should I say, interesting fact is that I downloaded the NAS navigator 2 Macintosh Version. That is supplied by Buffalo that is a standalone application which allows you to configure these systems. Surprisingly, this Application does work on Mavericks, but all it allows me to do is access the backend utility and diagnostics and configuration menus of the Terra station. Unfortunately I am not able to actually contact or connect to the data volumes within the Tara stations. So at least I know that the Maverick system can communicate with the back end of the Buffalo NAS TeraStation, but clearly this is a problem with Mavericks new networking software. It's quite discerning and quite frustrating that Apple's Mavericks, their most innovative and newest and best operating system available on the market, all of a sudden has made so many problems for so many of us who use now as for external volumes running on other systems. It is quite frustrating and I have to say there's nothing other than the fact that Mavericks is the problem. It has to be, there would be no other reason why this would be the case.

I have tried every fix in the book and cannot get this to work. Tried the CIFS workaround. The volume will initially mount but after trying to move around the folder hierarchy, we get disconnected and the log shows the following:

4/2/14 10:21:21.107 AM mds[55]: (Normal) Volume: volume:0x7f987c08d000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/firmwaresyncd.8vAO0l

4/2/14 10:21:21.153 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “GROUP PROJECTS” couldn’t be opened.")

4/2/14 10:21:21.153 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “GROUP PROJECTS” doesn’t exist.")

4/2/14 10:21:21.153 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “BMCC-FileShare” couldn’t be opened.")

4/2/14 10:21:21.154 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “BMCC-FileShare” doesn’t exist.")

4/2/14 10:21:21.154 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “bmcc” couldn’t be opened.")

4/2/14 10:21:21.154 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “bmcc” doesn’t exist.")

4/2/14 10:21:21.154 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “Royalty Free” couldn’t be opened.")

4/2/14 10:21:21.154 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “Royalty Free” doesn’t exist.")

4/2/14 10:21:21.658 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “GROUP PROJECTS” couldn’t be opened.")

4/2/14 10:21:21.658 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “GROUP PROJECTS” doesn’t exist.")

4/2/14 10:21:21.658 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “BMCC-FileShare” couldn’t be opened.")

4/2/14 10:21:21.658 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “BMCC-FileShare” doesn’t exist.")

4/2/14 10:21:21.658 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “bmcc” couldn’t be opened.")

4/2/14 10:21:21.659 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “bmcc” doesn’t exist.")

4/2/14 10:21:21.659 AM sharingd[194]: getVolumeRefNumForURL::CFURLCopyResourcePropertyForKey(NSCocoaErrorDomain, 256, "The file “Royalty Free” couldn’t be opened.")

4/2/14 10:21:21.659 AM sharingd[194]: SDConnectedBrowser::getResourceValue(NSCocoaErrorDomain, 4, "The file “Royalty Free” doesn’t exist.")

4/2/14 10:21:38.511 AM ReadKit[175]: Sync timer fired

4/2/14 10:21:39.066 AM NetAuthSysAgent[683]: smb_mount: mount failed to URBSVR01/Sametime, syserr = Invalid argument

4/2/14 10:21:44.073 AM NetAuthSysAgent[683]: smb_mount: mount failed to URBSVR01/Employees, syserr = Invalid argument

4/2/14 10:22:11.736 AM mds[55]: (Warning) Volume: vsd:0x7f987c08d000 Open failed. failureCount:4 {

DisabledRecycleCount = 4;

}

4/2/14 10:22:14.094 AM Console[690]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.

I used cifs://ip instead of smb://ip to regain access to my server, and it worked like a charm.

I found these sources that helped me:

http://support.apple.com/kb/HT5884

http://www.zdnet.com/mavericks-smb2-problem-and-fixes-7000022519/ (bit of a hack)

http://hints.macworld.com/article.php?story=20131122083837447

(Trying to stay on topic replying to Ruprest.)

Here's what I did:

https://discussions.apple.com/thread/5470235?answerId=23784533022#23784533022

Grab a copy of Bonjour Browser and make sure all the Mac's with shares are advertising Samba. Once they are, you should be good sharing between all Mac's with Mavericks. Should clear up the Mac to Windows sharing too.

I know everyone's either disabling SMB for AFP or disabling SMB2, but I wouldn't:

http://appleinsider.com/articles/13/06/11/apple-shifts-from-afp-file-sharing-to- smb2-in-os-x-109-mavericks

Hi Troy and many others who are experiencing this issue of:

1. Client side: accessing from this mac
   • kernel[0]: smbfs_set_create_vap: smbfs_setattr, error 5
   • kernel[0]: smb_ntstatus_error_to_errno: Couldn't map ntstatus (0xc000010c) to errno returning EIO
2. Server side (services host | where the files reside on a network)
   • we have OSX Server for Mavericks (V3.1.1)
   • files systems, folders and files/objects administered using OD with groups etc permissions
   • File Sharing share points in both AFP and SMB, with OSX ACL management

Here's what we successfully did. This is 100% reliable although is a workaround.

What's well known when remote server is sharing via SMB on OSX Mavericks 10.9.x.

• network (remote) file sharing access through the default connect Finder default UI over SMB on Mavericks (i.e. using OSX Server File Sharing with "Share over SMB" ticked.. (as SMB2)) using the FINDER drag and drop on OSX 10.9.x yields the familiar Finder UI error -36 message: "The Finder can’t complete the operation because some data in [some-object-name[ can’t be read or written. (Error code -36)"
• network (remote) file sharing access through the default connect Finder default UI as "Share over AFP" ticked only works as documented using finder Drag and Drop (no SMB)
• network (remote) file sharing access through the default connect Finder default UI over SMB and AFP on Mavericks (i.e. using OSX Server File Sharing with "Share over SMB" & Share over AFP" both ticked.. (as SMB2)) using the FINDER drag and drop on OSX 10.9.x yields the familiar Finder UI error -36 message: "The Finder can’t complete the operation because some data in [some-object-name[ can’t be read or written. (Error code -36)"
• accessing specifically SMB using Finder Go / "Connect to Server" (+K) works because it accesses as SMB1 (not Apples SMB2 implementation on OSX.10.9

  smb://warwick@rendernode-09/renderpool/... blah blah

• accessing specifically SMB using Finder Go / "Connect to Server" (+K) works

  cifs://warwick@rendernode-09/renderpool/... blah blah

• and ofcourse AFP using Finder Go / "Connect to Server" (+K) always works regardless of the specification in OSX server's File sharing (Share over AFP" or "Share over SMB"

  as far as we have experienced 🙂

• any windows platform users accessing the said shared file systems seem to connect as SMB1 - not sure of the caveats.
  • windows 7, windos 8 pro and XP it seems... I'll stand corrected.
  • also those under a VM (parallels )

Our experience with our Highly Valued Users is that :

1. need access in both windows (smb reuiqred) and macosx platforms between all machines from any machines as athentication and authorisation ACL's permit.
2. wont tolerate anything manual to connect to servers tah are SMB2 services

   no mounting scripts, automator or login items .. etc etc

3. just want the file shares in the OSX FINDER or teh WiNDOWS Explorer etc etc
4. keep it simple..

Solution: (work around)

This is a well known/ well documented in many forums as a Work Around to make it all work as it did in Mac OSX 10.8 before the SMB2.

• we enabled SMB1 on ALL mac systems until SMB2 stability is realised
• on EACH MACOSX 10.9.x mavericks machine issue this command to restrict the use of SMB on the whole system for all users and services to SMB1 (not a single user)
  1. unmount all the remote shared file systems that are services by SMB2 current (macs?)
  2. issue this command in Terminal.app: sudo sh -cv "echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb1_only' >> /etc/nsmb.conf"
• when all OSX 10.9 machines have been dealt with , remount the network file systems serviced by SMB and access normall through the finder's "SHARED" interface
  • no need to specifically mount as CIFS nor SMB
  • assume all FILE SHARING authentication and authorisation is correct, there will be no more ""The Finder can’t complete the operation because some data in [some-object-name[ can’t be read or written. (Error code -36)" errors! 😉
  • there may be seme minor performance impact , although I've not experienced it yet. we use a dedicated set of LAN's through switches... this may vary to taste.

Summary:

• Although this implementation works well (it's well documented) , it's a workaround that is only required with a mix of SMB2 and MACOSX 10.9.x and windows accesses.
• when there is no need for windows, just use "Share over AFP" in the OSX Server's file Sharing.
• One needs to follow up after any OSX 10.9.x maintenance (updates) because it may be disabled again. (the /etc/nsmb.conf) is altered or removed.

Post your results for others to see.

Warwick

Hong Kong

Just converted to Mavericks. Couldn't access Buffalo Terastation.

I Enabled FTP on the device and access it via: Finder > Connect to server >ftp://ip.address. e.g. ftp://192.168.1.20 ...I had to hardcode the IP address as part of the Terastation configuration so I knew the specific IP address to ftp to.

It seems to work about 75% of the time. Occasionally, the shared folder comes up empty, in which case I dismount (move to the trash) the mounted drive and try again.

Once connected via ftp I can move / copy files to from it using the finder, and it seems very fast.

I'm another sucker that told people to upgrade to Mavericks. I sure look dumb now.

I am on 10.9.3 and can't connect to a samba share on a linux server via openvpn. The suggestions of using afp or cifs does not help.

Hi Warwick, thanks for your help. Incredible help! I managed to detect NAS after following your instructions. Strangely tonight, it couldn't. I went through the Terimnal sudo approach and this time, I couldn't type in password in terminal (previously, I could). I am not sure why the situation has reverted. Any advice will be greatly appreciated!!!

Hi pgohmac, thanks . The addition of the /etc/nsmb.conf should be permanent unless you delete it yourself. Strange that your appliance does not show up.

Regarding the response of any password in the terminal.app.. it does not echo passwords. Try it again . just type your password and press the return key. It won't show. If your password is wrong you will receive two subsequent prompts and then it will fail the command attempt.

Try again.. it should work.

Post your results for others to see.

Warwick

Hong Kong

Hi Warwick, thanks, I managed to get through password stage. Sadly, it didn't work. Frustrating as I have seen it work for me two days back. I was looking for nsmb.conf in the Mac/Library/Preferences but the only nsmb that showed up in the search was a nsmb.conf5 (last opened in Sep 13). I didn't reverse the command after it worked. Not sure why I am not able to locate nsmb.conf. Anyhow, thank you very much taking time with my query. It is greatly appreciated.

Patrick

Hi Patrick. Just check again. You need to make the addition to /etc/nsmb.conf. I'm unaware of what /mac/library/preferences" is.

On terminal use "mdfind nsmb.conf" for example

The system wide parm file is on the ROOT file system /etc/ folder

Use finder: cmd+shift+g and type "/etc" and press ok

Don't add this stuff to your home ~/library/presences.

Try to follow instructions in detailed post.

I apologise if I misunderstand your reply.

Post your results for others to see

Warwick

Hong Kong

Hi Warwick, thanks again. I won't trouble you further. You have been a good help. Regrettably, I don't know what more I need to do. Sorry, a layman here... not sure how to get results to post for all to see. I did the mdfind nsmb.conf command and this is what I see -

Patrick-Gohs-iMac:~ patrickgoh$ mdfind nsmb.conf

/Volumes/Seagate BU/Users/patrickgoh/Library/Caches/Metadata/Safari/History/http:%2F%2Fhints.mac world.com%2Farticle.php?story=20131122083837447.webhistory

/Volumes/Seagate BU/Users/patrickgoh/Library/Caches/Metadata/Safari/History/http:%2F%2Fcammodude .blogspot.de%2F2013%2F10%2Fos-x-109-mavericks-workaround-for-smb.html.webhistory

/Volumes/Seagate BU/usr/share/sandbox/com.apple.netbiosd.sb

/Volumes/Seagate BU/usr/share/man/man1/smbutil.1

/Volumes/Seagate BU/usr/share/man/man5/nsmb.conf.5

/Volumes/Seagate BU/usr/share/man/man8/mount_smbfs.8

/private/etc/nsmb.conf

/usr/share/man/man5/nsmb.conf.5

/Users/patrickgoh/Library/Caches/Metadata/Safari/History/http:%2F%2Fwww.zdnet.co m%2Fmavericks-smb2-problem-and-fixes-7000022519%2F.webhistory

/Users/patrickgoh/Library/Caches/Metadata/Safari/History/http:%2F%2Fhints.macwor ld.com%2Farticle.php?story=20131122083837447.webhistory

/Users/patrickgoh/Library/Caches/Metadata/Safari/History/http:%2F%2Fcammodude.bl ogspot.sg%2F2013%2F10%2Fos-x-109-mavericks-workaround-for-smb.html.webhistory

/Users/patrickgoh/Library/Caches/Metadata/Safari/History/http:%2F%2Fcammodude.bl ogspot.de%2F2013%2F10%2Fos-x-109-mavericks-workaround-for-smb.html.webhistory

/Volumes/PG WD/usr/share/man/man5/nsmb.conf.5

Patrick-Gohs-iMac:~ patrickgoh$

When I type in your main command, this is what I get after typing in the password -

Patrick-Gohs-iMac:~ patrickgoh$ sudo sh -cv "echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb1_only' >> /etc/nsmb.conf"

Password:

echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb1_only' >> /etc/nsmb.conf

Patrick-Gohs-iMac:~ patrickgoh$

You have mentioned to unmount shared file systems. I don't know how to unmount the NAS from my Shared. While I can login into NAS as Admin and see my timemachine backup, I cannot detect this NAS to its settings via synology assistant.

No obligation to advise. I am already grateful for your help.

Thanks,
Patrick