Can't connect to SMB share after upgrade

Also can't connect to Samba shares.

In 10.9.4 the error was a PreXP / deprecated error in the Console log, as I was connecting to Windows 98 share.

I was able to access my smb share by using MuCommander, and copy files from Win98 to Mavericks 10.9.4.

MuCommander doesn't properly copy files the other way however. Files are transferred back with blank created and modified dates, and PDFs are copying back with images corrupted. Thus, this isn't a perfect solution.

10.9.5 is now out, with improved Samba / SMB connections.

I just upgraded.

Now, the PreXP/depreciation error is no more!

I've got a NEW error:

NetAuthSysAgent[274]: doConnectWithTimeout: nb_sockapi_connect failed, errno=61 Connection refused

I just tried using the commander line connection method also:

/sbin/mount_smbfs

(which is explained here: http://forums.macrumors.com/showpost.php?p=13022967&postcount=9 )

....and that gives me the original error in the console log:

kernel[0]: smb1_smb_negotiate: Support for the server UG has been deprecated (PreXP), disconnecting

So either I need MuCommander to actually transfer files with a created and modified date.

Or I need to solve the Finder's Samba errors, =P.

For now, I'll just use my old G4 as a go-between, and connect to my Samba share via the G4, copy files to the G4, and then have Mavericks connect to the G4 via Apple File Sharing to get the files.

Found a better solution than keeping an intermediary computer switched on all the same.

Download & Install Oracle's Virtual Box.

Setup a Windows XP virtual machine.

(select the appropriate network and sharing settings)

Install Windows XP SP3 onto the virtual machine (you'll need a valid licence key).

And that's it.

I run a virtual box version of Windows XP on Mavericks every time I want to connect to an older Samba share.

It just works.

I have my Mac OS hard drive setup to shared with the virtual Windows XP machine, so I can drag and drop anything from the Samba share to my Mac hard drive and vice versa, within the emulated windows environment.

I would have loved to run a virtual Snow Leopard instead of Windows XP, but couldn't get it booting correctly, =S. So went with XP instead. Simple, =).

Has anyone found an equivalent under Yosemite?

A number of people have a problem with samba under Yosemite because it now defaults to SMB3 and certain HP printers (that have the facility to scan to a network folder using SMB) can't talk SMB3. So I need to get Yosemite to fall back to SMB2 or SMB1 and I've tried this (and putting it in /etc) and it seems to have no effect on samba under Yosmite - so not sure if it is configured differently in OS X 10.10?

I've only just installed Yosemite on an external hard drive, so haven't had time to try Samba out on Yosemite yet.

As mentioned in my post above,

running a virtual copy of Windows XP solved all my Samba problems.

If you share your Mac hard drive, or even just a folder, with the virtual Windows XP, you can have your printer scan to a Windows XP folder, and then copy the files over to your Mac. VirtualBox can help you run virtual operating systems, and is available for free, for personal use.

That said, if these are current HP printers, perhaps HP will update drivers or firmware, for them to work with Yosemite and SMB3 in due course?

Sorry I'm not directly answering your question. I'm sure there is a way to get Yosemite using SMB2 or SMB1.

Have you tested to see if the terminal commands used before, still work in Yosemite?

If Yosemite is to be the Samba server, then you can also look at solutions such as SMBUp or Dave, and see if they work with Yosemite or not.

Again, I'm writing this as a Mavericks user, who's only just put Yosemite on an external hard drive, and hasn't experimented with any Yosemite Samba solutions yet.

Do post back and let us know how you get on / what works! =).

Thanks for your reply ajmetz.

My environments is OS X only - so installing Windows won't help me.

Yes, I've tried the various work arounds for forcing OS X Samba to use either SMB1 or SMB2 but neither of them have any effect under Yosemite. (The two are creation of an nsmb.conf file and use of com.apple.smb.server.plist - both are documented as control config for Samba on previous versions of OS X, but neither works on Yosemite).

I have now found a workaround - but it's crude - it involves installing a third party Samba implementation and bypassing Yosemite's SMB entirely - which I guess is a slimmed down version of your approach!

But it has to be possible to control config of OS X Samba somehow - if Apple have changed the way the config files work, presumably there is something new - it would just be nice to know what it is!

hedgert wrote:

But it has to be possible to control config of OS X Samba somehow - if Apple have changed the way the config files work, presumably there is something new - it would just be nice to know what it is!

Indeed it would! =)

Hopefully someone can fill us in soon, =).

hedgert wrote:

I have now found a workaround - but it's crude - it involves installing a third party Samba implementation and bypassing Yosemite's SMB entirely - which I guess is a slimmed down version of your approach!

Which third party Samba implementation did you go for in the end?

Does it integrate reasonably well?

There seem to be some answers via a simple smb Yosemite Google search.

Running Mavericks right now, so haven't tested this, but what do you make of the likes of:

http://www.mac-forums.com/forums/os-x-operating-system/316688-samba-mounts-yosem ite.html

I used smbup - it doesn't integrate with the settings/file sharing panel (that doesn't work while smbup is installed and operational).

Details of what I did here:

http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-Setup/setup-scan-to-netw ork-folder-yosemite/m-p/4672514#M167310

There's nothing out there relevant to Yosemite that I've found. Your mac-forums link 2 above is similar to others out there - it's generic stuff about how to configure samba on UNIX - that particular post is about the config approach used for samba under Debian. It talks about adding a setting to smb.conf - but OS X doesn't use a config file called smb.conf

This is unacceptable, I have the newer osX, El Capitan. I Still have this problem with SMB connection with other equipment and older osX. This is a stupid think that apple repeat year to year.

<Edited by Host>

...or you can update the systems that El Capitan is trying to connect to. El Capitan is refusing to connect to those older Samba (Windows file sharing) services because they're insecure. Update the software or firmware on the device or computer you're trying to connect to.

That simply isn't true. This still occurs on when connecting to Samba 4 servers running the very latest version (4.3.6). Apple's SMB implementation is still not compatible with Microsoft's or the Samba project's implementations.

This may be a SMB vs. SMB2 issue. I upgraded from OS/X 10.11.4 El Capitan to 10.11.5 and all connections using smb://<server> failed. You can find a solution here.

https://knowshare123.wordpress.com/2016/05/20/unable-to-connect-macbook-to-nas-s erver-after-upgrade/