Can't connect to SMB share after upgrade

Hi Pat, yeah this is a bit of a bugger. Your work looks quite sound. I suggest we look at the usual diagnostic messages. You can access these using the /applications/utilities/Console.app. The particular one that will be of interest is your good friend /var/log/system.log....

Investigation:

I suggest you review at the logs above after some interactions with your synology appliance (step 4 below) . There will be some diagnostic information that will be vary helpful

You can perform some deliberate use of the Finder with your MAc's file system and those on the synology appliance to generate (aggrevate) errors.

Instructions

1. prepare the synology appliance via ethernet etc.. make sure it looks like it's on your lan (wifi or cable). It's probably ready to go anyway

2. open up the /applications/utilities/Console.app

   in the Console list (left hand side), select system.log and make sure its scrolled to the end .. the current time

3. open a new FINDER window and make sure you can see the file systems from the Synology appliance in the SHARED area of the Finder window

   DO NOT ATTEMPT to mount is them specifically using a MOUNT or "connect to server" [+k] - this defeats the purpose of the diagnostics

4. now perform sem DRAG AND DROP actions form you mac's internal file systems to the file systems on the Synology. - this SHOULD generate errors in the FINDERs UI

   hopefully you will see the usual -36 error

5. Now, check the console system.log for any RECENT errors in the last minute of the action from STEP 4. You may see some errors.. hopefully..
6. Collect these (select and copy) and post them into a subsequent post here. No more than 10 lines I think.

   PLEASE don't post 10000's of unrelated lines.. I know you won't! 😉

Suspicion / Speculation

It MIGHT be the case tha you have some invalid or incorrect enties in eth SYSTEM KEYCHAIN. THese are very easy to recosile and correct.

You may see essages like:

• NetAuthSysAgent[3663]: NAHSelectionAcquireCredential The operation couldn’t be completed. (com.apple.NetworkAuthenticationHelper error -1765328228 - acquire_kerberos failed warwick@LOCAL: -1765328228 - unable to reach any KDC in realm LOCAL, tried 0 KDCs
• dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7f87e9a17310 FFFFFFFF DDDDDDDD)
• netfs_GetServerInfo returned 65
• sharingd[372]: SDSharePointBrowser::handleOpenCallBack returned 6
• etc etc

Anyway, this is worth pursuing. OSX and your mac are just a set of tools. The tools should work... and they usually do.

Post you results for others to see.

Warwick

Hong Kong

Warwick, you have given me hope again. Thanks. Will try the steps.

Reinfire,

Your CFIS:// solution worked, thanks so much!!!

My 2 cents on this: I wouldn't hold my breath on Apple fixing this SMB issue. As much as I enjoy using my MBP, osberving Apple over the last few years, it's very clear it's their way or the highway, no matter how many people complain, cry foul, make suggestions for improvements, et cetera.

Glad to see there are people out there willing to find and share workarounds to make a product usable, as it should be.

Hi Artur, using a SPECIFIC connection will always force that connection to SMB1... it doesn't help in a general sense with the FINDER UI.

A well known workaround in any case.

w

Hi Warwick, thanks.

1) When NAS appeared under Shared, it was connected automatically as GUEST. I then dragged internal files from Mac to a Public folder in my NAS. Initially, I dragged and dropped out of the public folder and message came out saying I need to click authenticate (but i didn't know where to click).

2) No error came out in the Finder.

3) Console messages... Any hope? 🙂

May 29 15:21:38 Patrick-Gohs-iMac kernel[0]: ASP_TCP Detach: Reply queue not empty?

May 29 15:21:38 Patrick-Gohs-iMac kernel[0]: ASP_TCP CheckReqQueueSize: increasing req queue from 32 to 128 entries. so 0xffffff801e98d650

May 29 15:22:10 Patrick-Gohs-iMac.local mds[35]: (Normal) Volume: volume:0x7fab83c05000 ********** Bootstrapped Creating a default store:1 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Public

May 29 15:22:13 Patrick-Gohs-iMac.local sharingd[193]: dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7fc0a04891d0 FFFF0007 DDDDDDDD

May 29 15:22:14 Patrick-Gohs-iMac.local WDQuickView[228]: Updating service information

May 29 15:22:21 Patrick-Gohs-iMac.local Finder[185]: sandbox extension creation failed: file system representation creation error for path: [/Users/patrickgoh/Desktop/User's Guide.pdf]

May 29 15:22:21 Patrick-Gohs-iMac.local Finder[185]: __CFPasteboardCreateSandboxExtensionDataFromCFData : failed to obtain sandbox extension data for url [file:///.file/id=6571367.7975496]

May 29 15:22:27 Patrick-Gohs-iMac.local Finder[185]: No valid sandbox extension for item: [1] of flavor: [public.file-url] was created.

May 29 15:22:27 Patrick-Gohs-iMac.local Finder[185]: Failed to get a sandbox extensions for itemIdentifier (1). The data for the sandbox extension was NULL

May 29 15:23:11 Patrick-Gohs-iMac.local sharingd[193]: dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7fc0a054a590 FFFF0007 DDDDDDDD

Hi Pat, thanks for posting some dialogues. There's some insight here in these two messages.

May 29 15:22:13 Patrick-Gohs-iMac.local sharingd[193]: dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7fc0a04891d0 FFFF0007 DDDDDDDD

.....

May 29 15:23:11 Patrick-Gohs-iMac.local sharingd[193]: dnssd_clientstub DNSServiceRefDeallocate called with invalid DNSServiceRef 0x7fc0a054a590 FFFF0007 DDDDDDDD

However before we get too excited 😉, I'm curious to the method you used. I understand from you post that you:

• can see your synology appliance in the Finder sidebar SHARED and
• that you connected as GUEST (?) and then
• that you CLICK on it and can see the contents and
• subsequently perform the drag ad drop and NOT be prompted for authentication.. (a result of guest maybe)

Would you be able to authenticate into your Synology as you (patrick) or what ever the synology appliance wants? Do this instead of GUEST.The reason is that I'd like to see the DNS failure is not simply caused by a default connection method. Instead let's connect purposely.

Instructions:

1. make sure the file systems on the Synology appliance are visible in the Finder's Sharing Sidebar as you did in your previous collection effort.

   (for other readers, make sure (+,) Finder Preferences / Sidebar / Sharing/ Connected Servers is TICKED )

2. DOUBLE CLICK in a specific synology appliance file system and CONNECT AS (PLEASE don't use the GO menu.. see picture. In this case I've selected the server "macmini-02"

   

3. provide your LOGIN credentials and tick "remember this password in my keychain"

   we can see the keychain entry for this in your local LOGIN as a kind "network password"...

4. assuming you have been auththenicated, would you perform the DRAG and DROP test again please.

   it should generate some more diagnostics.

5. Would you collect those few lines and post them here please?

Suspicions and Speculation:

those messages dnssd_clientstub DNSServiceRefDeallocate I mentioned above are to do with our old mate Bonjour. So... before we get the surgeons knife out, would you post those diags from step 5... here.

Post your results for others to see.

Warwick

Hong Kong

Hi Warwick, I'm sorry to trouble you.

From screen capture below, my NAS will automatically connect to a GUEST user profile I have created. This profile has access to a Public folder. I can also connect as Admin. However, I cannot get into the NAS settings via IP address or Synology Assistant (below error message will show). The most frustrating part was that I did managed to get into the settings after following your steps (before I wrote to you).

When I drag and drop a file into PUBLIC, there will be no error. However, if I drag and drop file into the space out of Public in this Guest Profile, I will see the below error.

The NAS is my time machine backup. The time machine did not work initially and then it did. Now, I am validating if it will work again.

Many thanks again,

Patrick

Hi Patrick.. hmm.. looks troublesome. I believe you still have an issue with the Bonjour agent that is related to your local keychain.

Would you issue this command in the terminal. It will keep going so sop it after 10 seconds, gather the output and post it back. Make sure to delete/remove/redact anything that is confidential.

this merely lists any of the bonjour devices on your local network.

The command is: .. copy and paste it into Terminal.app

dns-sd -B _afpovertcp._tcp

Please gather (copy and paste) the output from the terminal and post it back in a subsequent post when you can.

Post your results for others to see.

Warwick

Hong Kong

hi Warwick, thanks again. I sincerely appreciate this but after this post, i will not want to trouble you further. I hope 10.9.4 will help. After the command, only this part came up (waited 15 mins for more and nothing came out). What do i look out for that is "confidential" to delete in future posts? Thanks again, Patrick.

Last login: Mon Jun 2 10:30:53 on console

Patrick-Gohs-iMac:~ patrickgoh$ dns-sd -B _afpovertcp._tcp

Browsing for _afpovertcp._tcp

DATE: ---Mon 02 Jun 2014---

12:06:21.771 ...STARTING...

Timestamp A/R Flags if Domain Service Type Instance Name

12:06:21.771 Add 3 4 local. _afpovertcp._tcp. Patrick Goh’s iMac

12:06:21.771 Add 3 6 local. _afpovertcp._tcp. Patrick Goh’s iMac

12:06:21.771 Add 2 4 local. _afpovertcp._tcp. patrickgoh

Hi Patrick, thanks for the reply. The bonjour device listing looks fine and it shows the two points for you iMAC.. Are there any other devices that you think should be there?. I don't see the synology appliance there. I DONT own one. I did imagine that the device like most printers and others support Bonjour. Just wondered if there's a simple way to enable it on Synology appliance?

Timestamp A/R Flags if Domain Service Type Instance Name

12:06:21.771 Add 3 4 local. _afpovertcp._tcp. Patrick Goh’s iMac

12:06:21.771 Add 3 6 local. _afpovertcp._tcp. Patrick Goh’s iMac

12:06:21.771 Add 2 4 local. _afpovertcp._tcp. patrickgoh

by confidential, I meant anything that you didn't want to make viewable in the post. 😝

Further:

What I was anticipating was a list of bonjour devices that might have included your synology device. This would be the way to connect rather than a specific connection. This should appear regardless of the fle system protocol being orchestrated at the device (synology, printer etc)

Would you try this is you can:

From your previous posts, I think there MAY be some issue with your System keychain or entries in your local key chain. So .. tty this:

1. open /applications/utilities/Keychain Access.app (+⇧+U)
2. under the RED led (top left) UNLOCK the pane so you can administer it.
3. in lower left sideboard, select "All Items".. it may already be selected
4. in the filter TOP RIGHT CORNER, type in the name or the IP address of your Synology appliance. It may be the name of you gave it to refer to it.
5. select these entries for the synology and DELETE them
6. reply to your password as needed.
7. now flush the DNS cache on you imac using these two commands in the terminal .app
   • dscacheutil -flushcache
   • sudo killall -HUP mDNSResponder
8. for best RESULTS, restart and log back into your MAC again
9. does your synology device appear in the FINDER's SHARED list?

report back

Post your results for others to see.

Warwick

Hong Kong

Hi Warwick, thanks for your email.

Before I went into your proposed 9 steps in your last post, I went into your earlier command (dns-sd - B....) and same results came out. No synology. To answer your last question in point 9, my synology device is showing up in the shared list all these while. My challenge is that i cannot detect this NAS through the Synology Assistant or the web to look into the settings of the NAS. In your keychain access steps, i don't see the synology disk station.

Will Yosemite change this issue?

Many thanks again,

Patrick

Hi Pgohmac, Same issue here and now buying new macs for my organization won't let me downgrade to 10.8.5. Sad. And to answer your last question, Yosemite Beta2 is still broken for SMB:// or CIFS://

Very poor re-write of SMB by Apple coders, its sad too see that they don't support the community by making things work with other platforms.

Now my job is to find a way to downgrade our Brand new MacBook Pro's to 10.8.5.

Thanks Apple for ruining something that was working.

Good luck ladies and gentlemen.

Fred.B/

Reinfires 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

For those of you out there logging on using a domain that still have this problem after trying the SMB1 fix, I was able to fix this by making my account "mobile" in Users and Groups under System Preferences. It seems there's some sort of authentication issue that happens when you just log straight in to a computer on a domain.

So Reinfires solution does work. However I am still having a huge issue with uploading to network drives. Downloading from them is fine, however a client of mine is trying to upload to the drive (6GB file) and it is saying it will takes days before it uploads, which it eventually crashes instead of transferring.

Anyone have any idea of a workaround for the upload?