Can't connect to SMB share after upgrade

AlienCamel.com wrote:

Briolet wrote:

...

smb is now the default between two Marvericks macs

...

I'm not seeing this on our 10.9.1 Macs - still using AFP.

Where was this statement made or discovered by someone Briolet? I find that hard to believe.

Or did you mean to say SMB in general is the default, and specifically the SMB2 version is now the default in Mavericks?

I leave PC to come on Mac because of this kind of crap.

Mac was use to "plug it and it works" now I have 3 mac, they even on Maverick, and none of them can connect each other..

*** ???

Honestly.

I tryed alot of different ways...
Even on guest it doesn't work..

Did I have to bring my mac pro and my 2 laptops at apple store and crossing my fingers hoping it will work on my personnal network ??

Why even apple don't reply officially about these problem ??
Are we user, have to find and solve these problem alone ??

Hello Apple !? somebody is there ?

I tryed all your solutions online and it doesn't work !!
And reading this post seems all exept that :

"apple, it just works"

Joker !!! I am soo disapointed and for soo many reason !!

my next computer will not be a mac !!!!!!

After upgrading to Mavericks I can't connect to my NAS, a USB 2.0 drive connected to my WD My Net N750 router. Using workaround 2 from cammodude's blogpost worked for me (though workaround 1 didn't).

I'd like to chime in and hope it may help a few of you. It sounds like some of the issue are very similar to what I've been experienince since my Mavericks upgrade. I have not been able to connect to any of the external volumes on some of the specific XP systems running in our office. Some work fine and some work for a second or two and then I get permissions revoked.

Today, I decided to take the exteral volumes off of the USB bus and install internally into the PCs. That didn't work either. Then I noticed one interesting fact...

All of the hard drives that I could successfully connect to were formatted as NTFS. All of the hard drives that did not work properly were FAT32. So I tested some things....

I took one of the 2TB hard drives and moved all of the data to a safe clean drive. I then reformatted the 2TB hard drive as NTFS and moved the data back. Voila! It works now. It works internally or externally as a USB drive.

So the culprit, in my case, is the file structure and format of the drive. It seems Mavericks does not play well with FAT32 or FAT formatted drives on XP machines. Ironically, these FAT32 drives worked fine with Mavericks and Win7, but XP and FAT - NO WAY!

So I'm happy now, hopefully it may help some of you. I would be interested to know if reformatting to NTFS solves any of the problems you all are experiencing.

-Marc

My issues were all with NTFS drives, so personally I don't believe it's that.

That said, today's 10.9.2 update has the following in its list of fixes:

"

Improves reliability when connecting to a file server using SMB2

"

http://support.apple.com/kb/DL1726?

Wonder if this is the fix we've wanted?

iRatlsnake,

I was having no more issues with Mavericks UNTIL 10.9.2. It appears they have broken the SMB1/CIFS workarounds.

I've been using the SMB1/CIFS workaround with our Netgear ReadyNAS servers since installing Mavericks, and I haven't noticed any difference since updating to 10.9.2. The workaround is still working.

Is their any news on this issue yet apple? Yes the work around works, but were now on 10.9.2 and still their is no official resolution to this.

I want my mac back to auto discovering my SMB shares again, I hate having to search for PC's and servers by name.

minime649 wrote:

Is their any news on this issue yet apple? Yes the work around works, but were now on 10.9.2 and still their is no official resolution to this.

I want my mac back to auto discovering my SMB shares again, I hate having to search for PC's and servers by name.

Which issue are you referring to? This discussion got hijacked and there are numerous issues raised.

Hey,

I refer to the issue were on macs we used to be able to turn it on and it would in the network section auto find and show all available network resources, eg machines, servers and printers.

All this used to work perfectly prior to os mavericks, however now things like my buffalo ready NAS do not populate and my only successful means of connection is to cifs:// connect to it.

minime649 wrote:

Hey,

I refer to the issue were on macs we used to be able to turn it on and it would in the network section auto find and show all available network resources, eg machines, servers and printers.

...

Intersting, my Synology NAS has never shown a list of the mountable shares under any version of OSX. And Synology had to issue patches to fix SMB2 problems specifically with 10.9

Maybe you should also see if it's a Buffalo issue.

So in Mt. Lion we connected at work to Windows 2008 file server with smb://servername/folder and with Mavericks that failed.

Now with 10.9.2 it's fixed. It works again as usual. So I'm happy.

Hey just curious, I have an original Buffalo Tera Station and I see it in my network places, but how do I connect to it with Mavericks? It says:

There was a problem connecting to the server "gs-tera".

The version of the server you are trying to connect to is not supported. Please contact your system administrator to resolve the problem.

Any word? I hear maybe this model is so old that Mavericks won't connect to it. This one is 4x250GB and I would love to have that etra 1TB pf storage on my network.

Any suggestions? I don't even know what the default IP address of the device is. I would love to connect to the backend interfae and reformatt the entire drive,

Anyone?

I am on 10.9.2 connecting to a NetApp CIFS share and with the CIFS:// work around I am unable to connect to my share drive. If I use a domain admin account it works fine and I have no issues with copying files or placing files on the server but that with the old version of SMB.

Anyone heard of any new news regarding this issue?

I'm on 10.9.2 and it connects fine to Windows through smb://ip. The issue is that my PCs can see my Mac in the network folder but they can't connect at all. I've tried to execute the ip address in Run.exe. I've already attempted to force smb1, but none has changed. Maybe I didn't do it right because the terminal didn't show any sign of successfulness.

The only thing that worked is disable SMB sharing and uncheck the user in Windows File Sharing, reboot, re-enable SMB and user. It works 'till next reboot. I was kinda hoping for a more permanent solution.

Does anyone has the same issue? There's any workaround for this?