Digging through the console I found this telling error:
NetAuthSysAgent already_mounted: share <TIMEMACHINE> already mounted
TIMEMACHINE is my share name in this case. As the error suggests, Time Machine is trying to mount the share again which it can't do because it's mounted already. But wait! If I disconnect from the share will leave my list!
I will admit, I hadn't noticed that the defaults write command stopped working in Mavericks.
However, when I DO clean network mounts, instead of your one liner find and rm, I use this:
The manfile explains:
dot_clean -- Merge ._* files with corresponding native files.
I don't use the -m flag, but you may find it helpful in your situation.
After 2 months of (moderate) misery I've finally found the reason SMB didn't work with my Sierra Mac Mini.
TL;DR The reason was this installed kext:
com.intel.kext.intelhaxm (6.0.1) 8FF2C637-0A5E-367E-B007-5B08655B1E8A <7 5 4 3 1>
You can check if you have it installed with the following command from an ordinary Terminal:
kextstat | grep -...
umount is the opposite of mount. You'll need to know the name of the mount point - that is, the name in /Volumes that corresponds to that network drive.
Per man umount, umount may fail for any number of reasons, and the recommend command is instead diskutil:
diskutil unmount /Volumes/VolumeName
It depends on how this was set up to launch. From boot, Go > Connect to Server > (click the dropbox) and select clear recent servers, if not using any. Then go to System Preferences > Accounts and see if there is something set up in the Login Items tab related to the server and clear. Restart and test. If it continues I'd check Macintosh HD > Library > ...
Just tried, and this does work in Mavericks (at least for disabling .DS_Store not network shares):
defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true
You just need to remember to restart Finder as well:
When you access a file share, you could try using CMD + k in Finder (Connect to server), and then type the address as a CIFS or SMB path - ie.
cifs://my.server/SomeFileShare or smb://my.server/SomeFileShare
Disclaimer: I don't have Mavericks, and no access to my Mac right now. And I'm not even certain that Finder doesn't somehow jump on AFP anyhow.
Apple Filing Protocol is deprecated1, not "dead". There's a big distinction and that is being deprecated, it's still included and still works at the time of last development but it has been superseded by something else - in this case SMB2. It also means there will be no further development.
Will it stop working in future versions of macOS?
There will ...
This answer assumes a few things:
your iMac is already connected to the network (most likely via ethernet)
that your credentials are all setup (based on your question, they are)
that you’ve been given the host address for the share drive
To connect to the share drive, you should only have to:
Make sure the Finder is active
Press commandK (or, in the top ...
This is going to be a throughly unsatisfying answer, but it comes down to the fact that random network drives were not meant to be used as time machine backup targets.
I'd wager one of the things you did in your guide was to run a terminal command along the lines of:
defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
The smbutil command can dump the attributes for all shares or you can target one particular share and parse out the version string:
smbutil statshares -a
In the case of the listing below:
site-test-mbp01:~ me$ df
Filesystem 512-blocks Used Available Capacity iused ifree %iused Mounted on
I'm in a similar position at work, with a mixed environment. We use WinShortcutter, which is freeware. The allows you to right-click on a UNC path (such as \\FileServer01\topfolder\subfolder\shared.doc) and Open as Windows Link:
It's quite configurable as well, and allows drive mappings (so when you are sent a link that starts S:/folder, it will allow you ...
I had the same problem (1025 failures to open smb device, syserr = No such file or directory) and finally tracked it down to the /dev/nsmb0 device not being correctly configured because of a conflicting kext from a very old 3rd party app. If you cat /dev/nsmb0 and get "Device not configured", it's possibly a similar issue.
To solve it, I looked at all the ...
Your IT department shouldn't have just abandoned you at this point. They should have worked through it with you.
We can't really answer this without knowing more detail of the network setup there, but the basic premise would be to start from
Finder > Go > Connect to Server...
simply type smb://[address you should have already been given] & hit Enter.
There's a number of options for doing this, but the easiest way is to just use your Login Items. More specifically:
In the Finder, press CommandK (or click on the Go menu and select Connect to Server...)
Now enter the server address
Click on the Connect button
IMPORTANT: If you're a registered user, when entering your login details you must ensure you ...
If you're using Lion, you can use smbutil:
usage: smbutil [-hv] subcommand [args]
where subcommands are:
help display help on specified subcommand
lookup resolve NetBIOS name to IP address
status resolve IP address or DNS name to NetBIOS names
view list resources on specified host
dfs list DFS referrals
identity identity ...
Here's how I solved this problem - the scorched earth method - find all preference files with the server name and remove them.
Replace server_name with the name of the server giving you grief, replace file_name with the name of the preference files you find:
in a terminal:
sudo grep -R "server_name" .
for each file returned:
You could install Samba3 through Macports and then you'll have smbpasswd available again.
Install Xcode from Apple - If you download Xcode from the Mac App Store, be sure to use the Xcode preferences to subsequently download the command line tools or use the xcode-select tool to get the BSD command line tools placed in your path. MacPorts needs make, gcc ...
Prior to Mac OS X Lion, Mac OS X Client came with SAMBA Server and Client and what you defined to share was all that was shared. Since Mac OS X Lion, and continuing with OS X Mountain Lion and other releases of OS X, SAMBA has been replaced with SAMBX due to SAMBA moving to GPLv3. As a result SAMBA is basically broken in the OS since 10.7. The Mac OS X 10.7 ...
Got a workaround that worked in our organization.
This changes for macOS the SMB behavior to v2.
Changed the following setting in the /etc/nsmb.con file.
echo "[default]" >> /etc/nsmb.conf
echo "protocol_vers_map=2" >> /etc/nsmb.conf
I ran across this today which is one way to do it.
In summary for Mountain Lion:
Edit the file /etc/auto_master
Within add /- auto_smb
Within add /Volumes/mount_point -fstype=smbfs,soft ://user:pass@smbserver/share
The author goes onto mention a second method using the vifs command, but I've never tried that one and it seems to do ...
This seems to be a known issue as I remember running across a work-around the other day at TUAW:
Basically what they are telling you to do is replace the SMB:// in the Go > Connect To Server... dialog box with CIFS://
I gather this forces the Mac to use an older ...
I had a similar issue and this post solved it for me:
It may be the same discussion that Tetsujin references, but the setting to use is NOT "Send LM & NTLM - use NTLMv2 session security if negotiated" -- you should use "Send NTLMv2 response only". After I made that change, I connected to the share,...
The ._ files are AppleDouble files that are used to store metadata like extended attributes, ACLs, file flags, and resource forks.
To delete them, run:
find . -name ._\* -delete
You can see if files have extended attributes, ACLs, or file flags with ls -l@eO. The ._ files are usually created because files have extended attributes. You can use xattr -c to ...
I've found the solution. Two commands are needed in sequence:
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.smbd.plist
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist EnabledServices -array disk
Setup your NAS to export a NFS-share. Refer to the Synology knowledgebase how to do this or use the following how-to to set it up, fine tune and secure your set-up.
You may do it manually in the command line also:
Let's assume your media folder is /Shares/Media. Create or edit a file named exports in /etc. The example below restricts the access to computers ...
In case you haven't found a solution yet, in the guide I was following it never mentioned to run the tmutil utility to set the backup drive via command shell, so just run the following command on a Terminal and you will have the disk selected on Time Machine Preferences:
sudo tmutil setdestination "/Volumes/Time Machine Backups/"
Remember to change the ...
The problem is caused by Apple's home made implementation of the smb protocol. Using smb3 won't make a difference.
If you have control of the smb server (Samba?) then you can fix this issue by enabling the vfs_fruit module. If you are not using Samba then you'll need to find another way to enable "Alternate Data Streams" (ADS) and ...