Can't connect to SMB share after upgrade

NHC2365 wrote:

Hi Reinfire will this wordaround also fix the https:// share connection and force SMB1?

Unfortunately no. The workaround is only for the SMB process. The issue you are running into seems to affect multiple services not just SMB. Its seems you are dealing with more a network or general configuration centric issue.

Yes the https mount/share is providing major problems and I can not use it all without breaking the connection to the server. It even wipes out my connection with Outlook 2011.

Hi Reinfire,

Your solution doesn't solve my problem. Please take a look for the detail from terminal and advise for solution.

Thank you.

Last login: Thu Oct 24 11:47:50 on ttys000

Heng:~ KangYong$ echo "[default]"

[default]

Heng:~ KangYong$ ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only"

-bash: /Users/KangYong/Library/Preferences/nsmb.conf: No such file or directory

smb_neg=smb1_only

Heng:~ KangYong$

I wasn't able to get your fix to work. I followed the steps you laid out. It added the file to the directory and everything seemed to go according to plan, restarted and still no connection. Is there a step that I'm missing? Any help would be greatly appreciated. Thanks.

The Reinfire lin fixed my inability to open files on the SMB share. Fortunately I have not had issues connecting.

hhkangyong wrote:

Hi Reinfire,

Your solution doesn't solve my problem. Please take a look for the detail from terminal and advise for solution.

Thank you.

Last login: Thu Oct 24 11:47:50 on ttys000

Heng:~ KangYong$ echo "[default]"

[default]

Heng:~ KangYong$ ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only"

-bash: /Users/KangYong/Library/Preferences/nsmb.conf: No such file or directory

smb_neg=smb1_only

Heng:~ KangYong$

Hi hhyangyong,

Looks like you may have run into trouble with the >> characters when you performed the cut and paste. Before you hit the return button, make sure the entire line shows up and includes >> as well. It should all be on one line and not broken up across lines. Clearly from the above the >> is missing so I'd expect it not to work. Hope this helps.

echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf

dponinski wrote:

I wasn't able to get your fix to work. I followed the steps you laid out. It added the file to the directory and everything seemed to go according to plan, restarted and still no connection. Is there a step that I'm missing? Any help would be greatly appreciated. Thanks.

Hi dponinski,

When you say "no connection", what behavior are you seeing when to attempt to connect to a file server over SMB? Does it ever ask you for a login or password?

Also curious what file server / NAS you are attempting to connect to? All this solution does is force connections to use SMB1 which was what OS X 10.8.x used previously. If your mac connected before using 10.8.x then this should resolve it for you. Also just trying cifs://servername is another way to try it without creating the nsmb.conf file.

If your NAS / File Server doesn't support SMB1 to begin with, then the workaround that I provided won't work. Remember if you need to remove the file, you can use the instructions I provided or just navigate to that file and remove it.

Thanks,
Reinfire

Thanks a lot for the workaround. For me "option 2" (using terminal commands to create the nsmb.conf file with the smb1 protocol default) worked better than option 1 (not sure why...).

The file share connections are slow (not sure if they are slower than when I had OS X 10.8.5), but they seem to work in a stable way. (BTW I use smb together with VPN to access at home files that are remotely located at work).

Thanks again!

Hey Reinfire,

I tried the terminal fix, but it keeps asking me for username and password, which i never needed before, also when I add my username and password it doesnt accept it.

Any ideas?

thanks a ton.

FWIW, I've been speaking to Apple Support about this as I am also experiencing issues speaking to a server using SMB2. My current work around is to force the server or the Mac to use SMB1 which is obviously not the way forward. I am also in the process of providing logs etc to Apple in the hope that they can fix this bug.

In my case, I am unable to connect to a Synology server using SMB2. Disabling the SMB2 option and going back to SMB1 seems to work without any issue. AFP obviously works as per usual. I should point out that my 8.1 VM happily connects to the same server using SMB2 without issue.

We are using 10.9 which has only gone wild recently. Consequently if you are a business user, I'd probably hold off upgrading until this issue is resolved as this will be fairly critical in a corporate environment.

Hi Reinfire,

I tried by copied the whole code and hit Return but nothing happens.

I still not able connect to Windows shared folder.

This isn't working for me either (terminal command creating a file to force SMB1). One distinction may be that the share I'm trying to connect to is the UNC path from Active Directory. When used as my home directory on OSX, the computer will not login because of "an error." When using local home directories when the sytem logs the user in and it tries to mount the network share I get a "You do not have permission to access this server" message and the share won't mount, but I am obviously able to login. The share still mounts and works flawlessly under 10.7 Lion.

One curious thing about forcing the computer to default to SMB 1 is that accrording to the SMB release notes for Mavericks (link below), the OS is supposed to try SMB 2 first and then default back to SMB 1 automatically if necessary.

https://developer.apple.com/library/mac/releasenotes/HardwareDrivers/RN-SMB/inde x.html#//apple_ref/doc/uid/TP40007741

Has anyone ran into another possible solution or heard more from Apple?

Hi Troy and everyone else,

I just hang up the phone with Apple tech-supp.

My problem was that after the Meverick upg. I couldn't connect anymore to my Synology NAS smb share, using Command-K smb://ip_address_of_my_device.

Apple told me to use instead Command-K and type cifs://ip_address_of_my_device

For those of you trying to connect to a server share it should be the name or IP address of the server.

and this worked 🙂

If you suffered from the same issue as me this should do it. Try this and let me know.

FYI : This fixed my smb connection problem and now iMovie 9 can see and use my files, as before

BUT the new iMovie 10 (that comes with Maverick) does not support NTFS formatted Storage devices ANYMORE

That's a BUMMER and IT WILL AFFECT ALL USERS NOT USING STORAGE DEVICES FROM APPLE FOR IMOVIE

titust,

I was having problems connecting after Mavericks upg, but only when using VPN, as described by in an earlier post.

Changing from using smb:// to cifs:// resolved this issue for me, so thanks for passing along the tip from Apple Support.

Jim

Hi guys,

Woudn'have been nice if Apple released a communicate to let users know what changed exactly in Maverick in a more detailed manner ?

Like for example . . . if you used to do this . . . now in Maverick you do it like that . . .

I've never seen such a thing.

I'm glad it fixed your issue Jim.

Titus