10.9.2 Mavericks and can no longer connect to our SMB file share on the network.

I have a new information regarding this problem. After some communication with an Apple support engineer through the Bug Reporting tool I figured out that something is wrong with existent share connections. To be more clear, I suspect that after the update to 10.9.2 some login features have changed. Furthermore it seems that there is a problem with accessing shares through fully qualified domain names.

My suggestion for all affect by this problem is to delete all key chains related to SMB shares and also delete all known server connections. After reboot create a new share connection with the IP (not the fully qualified domain name) to the server and enter the credentials again.

Report here back if that is working.

Edit: Use the new server connection notation for connections:

smb://admin@192.168.0.1/share1

As in the example above.

First of I really want to say this (and this is a comment towards Apple not you surogat70!). How can there be something wrong with an exciting network connection? Is it something like "your holding your phone wrong?" Not here to attack someone, but Apple broke something. FIX IT!

As an reply to surogat: yes I did all you suggest. Deleted all know connection, and tried to get it going again.

After the "hack" I shared in this thread things seems to be "working", but very, very buggy. Network shares keep unmounting. Copying files is a nightmare, it's slow and it's more of a guess than certainty what permissions they have. Finder crashes, can't use quicklook. The "it just works" philosophy is fubar at the moment.

I only come to this forum if a got a real problem, which I can't solve even after many, many years of osx use.

I'm now using SMB2 with less problems. But I had to do that what I wrote. So SMB2 is currently working but the update had really breaked something.

I have come up with a work around which helps

Instead of using smb://192.168.1.5/example

try cifs://192.168.1.5/example

When i use smb my finder can crash

When i use cifs it works perfect

Hope this helps

Thank you
cifs doesn't help me. With cifs & smb networks shares work veeeeeeery slow and unstable :-(

Apple, make something!

I do not want come back to windows

I tried to directly use IP and specifiy the user name in order to connect to the SMB, it does not solve the problem. However, it worked very fast for one day (about 1 hour usage) but the next day it eventually ended up being very slow.

However, I noticed also some strange network "lags" outside the smb/smb2/cifs recently. For example, if I access a LAN Http Webserver (even when directly specify the IP), it sometimes takes quite a while to display a (small) plain text page. No other device has any issues with it - and mostly, the rMBP works also.

Further, while I ran some tests with Safari and connecting to the local http server, I noticed that windows domain name resolution shows really strange behaviour. The first time, it resolves the computer name instant to its IP, two minutes later it takes about 30 seconds. One would expect the opposite behaviour due to caching... Sometimes it is instant, sometimes it takes quite a while.

While I did those Http and name resolution tests, I was measuring network pings, yet I could not find any evidence of network drops. In fact, the connection was very stable.

I dont know whats wrong with OSX network stack, but there clearly are issues.

Note: All my tests and measurings were made using the wireless adapter.

Dseif's suggestion of using cifs:// to mount, solves the issue for me as well.

When I use smb:// to mount local Windows shares over a wired connection, the mount itself happens right away, but can take minutes before I can see files and folders. Once I can see them, navigating within them seems to be normal. Mounts to different shares on the same server also seem normal, as long as I leave at least one share mounted to that server. If I unmount them all, a new mount will again take minutes, before I can see files and folders again.

Oddly, when I use smb:// to mount a remote Windows share (~25ms latency through a VPN tunnel), I don't experience the same delays...the response seems the same as when using cifs://

Both the local and remote Windows servers I'm connecting to are running Windows Server 2012 R2, which I believe use SMB 3.0.

So apparently mounting with cifs:// uses the SMB1 protocol instead of SMB2.

As I understand it, yes.

I am glad others are having success with cifs://

I have had no issues at all with cifs:// but still got issues with smb://

At the end of the day as long as something works i am very happy

An other bug I believe related to this SMB2 thing, is that almost all my alias folders on the networked storage are broken.

It came to my attention when a old client contacted me in a panic. I set up a workflow for her, which worked for 5 years prior, with aliased folders, a lot of them. Almost nothing worked!

Can't restore the aliased folders because of permission issues (although "everyone" has read and write permissions). The same permission error can be said for some none aliased folders. Those permission issues (I'm not willing to investigate further) are persistent even when I revert my (clients) system(s) back to 10.8.

Thanks Apple, you just gave me days of work. Without pay though, client has no more money to spend. I want to keep the relations good, so I can't say no really.

After upgrading to Mavericks OS X 10.9.2, I could not connect to network shares on a Windows network, and kept getting "Connection Failed" errors every time I tried to connect. But I finally found a solution.

Firstly, using Finder --> Go --> Connect To Server --> smb://server_address --> Connect did not work. As suggested by others, I also tried cifs://server_address and that did not work either.

What worked for me was to use a Windows PC's cmd window to find the actaul IP address of the network share I am trying to reach. Example, "ping server_address". Once I found out the actual IP address of the network share, then I used it in the Finder. like this:

Finder --> Go --> Connect To Server --> smb://192.168.xxx.xxx --> Connect. When I did this, then I got a prompt to pick which volumes I want to mount. Voila, the server_address I was trying to reach was now mounted as a Share in my Finder.

I guess the only downside to this is if the IP address of the Windows server changes, then it will not connect. But if this happens I guess I will use the same process to determine the new IP address and remount the server loaction.

I hope this helps anyone else who is getting Connection Failed errors when trying to connect to a shared Windows server on a Windows network.

Thought the workaround using SMB1 was working until I found out all the Word Documents on the server were coming up Read Only.

It didn't matter which route I took to SMB1 as I tried all of them. So back to using SMB2, unless someone has a workaround to the problem with the workaround.

Using IP addresses instead of names makes no difference in behaviour for me...SMB is slow to bring up folder names, whereas CIFS is fast. I do not have a "read-only" problem when using CIFS (SMB v 1). Methinks that we're not all experiencing the "exact" same problem.

Sorry, my mistake. I am connecting using SMB to a Mavericks Server, not a Windows Server. Looked at so many discussions on the 10.9 SMB issue that I missed that this thread was about connecting to Windows Servers.