Trying to resolve ntlmv errros mounting CIFS network shares via fstab

Kernel: 3.4.2-2
WM: Openbox
About 6 months or so ago, which was after about a year on my current install with no issue, I began getting an ntlmv error when auto mounting samba shares at
boot.  Everything still worked but I continued getting an error message.
My fstab entry at that time looked like this:
//<LAN_IP>/<share name>/ /mnt/Serverbox cifs credential=/path/to/file,file_mode=0777,dir_mode=0777 0 0
The error I recieved looked like this:
CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
So I did what research I could on the error, found the "sec" option and discovered that adding the "sec=ntlmv2" option to my above noted fstab entry got
rid of the error message and everything still worked perfectly; that is until this weekend.
After upgrading both machines this weekend I noticed a new boot time error message and saw that my shares were no longer being mounted.
relevant boot log:
Mounting Network Filesystems [BUSY] mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
relevant everything log:
CIFS VFS: bad security option: ntlmv2
/var/log/pacman from the the weekend's upgrade:
[2012-06-16 13:03] Running 'pacman -Syu'
[2012-06-16 13:03] synchronizing package lists
[2012-06-16 13:03] starting full system upgrade
[2012-06-16 13:10] removed dbus-python (1.0.0-1)
[2012-06-16 13:10] upgraded linux-api-headers (3.3.2-1 -> 3.3.8-1)
[2012-06-16 13:10] Generating locales...
[2012-06-16 13:10] en_US.UTF-8... done
[2012-06-16 13:10] en_US.ISO-8859-1... done
[2012-06-16 13:10] Generation complete.
[2012-06-16 13:10] upgraded glibc (2.15-10 -> 2.15-11)
[2012-06-16 13:10] upgraded bison (2.5-3 -> 2.5.1-1)
[2012-06-16 13:10] upgraded libpng (1.5.10-1 -> 1.5.11-1)
[2012-06-16 13:10] upgraded cairo (1.12.2-1 -> 1.12.2-2)
[2012-06-16 13:10] upgraded libwbclient (3.6.5-2 -> 3.6.5-3)
[2012-06-16 13:10] upgraded cifs-utils (5.4-1 -> 5.5-1)
[2012-06-16 13:10] upgraded sqlite (3.7.12.1-1 -> 3.7.13-1)
[2012-06-16 13:10] upgraded colord (0.1.21-1 -> 0.1.21-2)
[2012-06-16 13:10] installed pambase (20120602-1)
[2012-06-16 13:10] upgraded pam (1.1.5-3 -> 1.1.5-4)
[2012-06-16 13:10] upgraded libcups (1.5.3-4 -> 1.5.3-5)
[2012-06-16 13:10] upgraded cups (1.5.3-4 -> 1.5.3-5)
[2012-06-16 13:10] installed python-dbus-common (1.1.0-2)
[2012-06-16 13:10] installed python2-dbus (1.1.0-2)
[2012-06-16 13:10] upgraded dconf (0.12.1-1 -> 0.12.1-2)
[2012-06-16 13:10] upgraded desktop-file-utils (0.19-1 -> 0.20-1)
[2012-06-16 13:10] upgraded firefox (13.0-2 -> 13.0.1-1)
[2012-06-16 13:10] upgraded freetype2 (2.4.9-2 -> 2.4.10-1)
[2012-06-16 13:10] upgraded initscripts (2012.05.1-3 -> 2012.06.1-1)
[2012-06-16 13:10] upgraded jre7-openjdk-headless (7.u4_2.2-1 -> 7.u5_2.2.1-1)
[2012-06-16 13:10] upgraded jre7-openjdk (7.u4_2.2-1 -> 7.u5_2.2.1-1)
[2012-06-16 13:10] upgraded jdk7-openjdk (7.u4_2.2-1 -> 7.u5_2.2.1-1)
[2012-06-16 13:10] upgraded kdelibs (4.8.4-1 -> 4.8.4-2)
[2012-06-16 13:10] upgraded libdrm (2.4.33-1 -> 2.4.35-1)
[2012-06-16 13:10] upgraded libglapi (8.0.3-2 -> 8.0.3-3)
[2012-06-16 13:10] upgraded liblrdf (0.4.0-9 -> 0.5.0-1)
[2012-06-16 13:10] upgraded libmysqlclient (5.5.24-1 -> 5.5.25-1)
[2012-06-16 13:10] installed khrplatform-devel (8.0.3-3)
[2012-06-16 13:10] installed libegl (8.0.3-3)
[2012-06-16 13:10] upgraded nvidia-utils (295.53-1 -> 295.59-1)
[2012-06-16 13:10] upgraded libva (1.0.15-1 -> 1.1.0-1)
[2012-06-16 13:10] upgraded mkinitcpio (0.9.1-1 -> 0.9.2-2)
[2012-06-16 13:10] >>> Updating module dependencies. Please wait ...
[2012-06-16 13:10] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-06-16 13:10] ==> Building image from preset: 'default'
[2012-06-16 13:10] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-06-16 13:10] ==> Starting build: 3.4.2-2-ARCH
[2012-06-16 13:10] -> Running build hook: [base]
[2012-06-16 13:10] -> Running build hook: [udev]
[2012-06-16 13:10] -> Running build hook: [autodetect]
[2012-06-16 13:10] -> Running build hook: [pata]
[2012-06-16 13:10] -> Running build hook: [scsi]
[2012-06-16 13:10] -> Running build hook: [sata]
[2012-06-16 13:10] -> Running build hook: [filesystems]
[2012-06-16 13:10] -> Running build hook: [usbinput]
[2012-06-16 13:10] -> Running build hook: [fsck]
[2012-06-16 13:10] ==> Generating module dependencies
[2012-06-16 13:10] ==> Creating xz initcpio image: /boot/initramfs-linux.img
[2012-06-16 13:10] ==> Image generation successful
[2012-06-16 13:10] ==> Building image from preset: 'fallback'
[2012-06-16 13:10] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-06-16 13:10] ==> Starting build: 3.4.2-2-ARCH
[2012-06-16 13:10] -> Running build hook: [base]
[2012-06-16 13:10] -> Running build hook: [udev]
[2012-06-16 13:10] -> Running build hook: [pata]
[2012-06-16 13:10] -> Running build hook: [scsi]
[2012-06-16 13:10] -> Running build hook: [sata]
[2012-06-16 13:10] -> Running build hook: [filesystems]
[2012-06-16 13:10] -> Running build hook: [usbinput]
[2012-06-16 13:10] -> Running build hook: [fsck]
[2012-06-16 13:10] ==> Generating module dependencies
[2012-06-16 13:10] ==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
[2012-06-16 13:11] ==> Image generation successful
[2012-06-16 13:11] upgraded linux (3.3.8-1 -> 3.4.2-2)
[2012-06-16 13:11] upgraded lirc-utils (1:0.9.0-16 -> 1:0.9.0-18)
[2012-06-16 13:11] upgraded mesa (8.0.3-2 -> 8.0.3-3)
[2012-06-16 13:11] upgraded mysql-clients (5.5.24-1 -> 5.5.25-1)
[2012-06-16 13:11] upgraded mysql (5.5.24-1 -> 5.5.25-1)
[2012-06-16 13:11] upgraded nvidia (295.53-1 -> 295.59-1)
[2012-06-16 13:11] upgraded opencl-nvidia (295.53-1 -> 295.59-1)
[2012-06-16 13:11] upgraded pango (1.30.0-1 -> 1.30.1-1)
[2012-06-16 13:11] upgraded pcmanfm (0.9.10-1 -> 0.9.10-2)
[2012-06-16 13:11] upgraded psmisc (22.16-1 -> 22.17-1)
[2012-06-16 13:11] upgraded smbclient (3.6.5-2 -> 3.6.5-3)
[2012-06-16 13:11] upgraded thunderbird (13.0-1 -> 13.0.1-1)
[2012-06-16 13:11] upgraded udisks2 (1.94.0-1 -> 1.94.0-2)
[2012-06-16 13:11] upgraded unrar (4.2.3-1 -> 4.2.4-1)
[2012-06-16 13:11] upgraded virtualbox-archlinux-modules (4.1.16-1 -> 4.1.16-2)
[2012-06-16 13:11] In order to use the new version, reload all virtualbox modules manually.
[2012-06-16 13:11] upgraded virtualbox-modules (4.1.16-1 -> 4.1.16-2)
[2012-06-16 13:11] upgraded xine-ui (0.99.6-5 -> 0.99.7-1)
[2012-06-16 13:11] Running 'pacman -Syy'
[2012-06-16 13:11] synchronizing package lists
[2012-06-16 13:12] Running 'pacman -Syu'
[2012-06-16 13:12] synchronizing package lists
[2012-06-16 13:12] starting full system upgrade
[2012-06-16 13:13] upgraded lib32-freetype2 (2.4.9-1 -> 2.4.10-1)
[2012-06-16 13:13] upgraded lib32-gnutls (3.0.19-1 -> 3.0.20-1)
[2012-06-16 13:13] upgraded lib32-krb5 (1.10.1-2 -> 1.10.2-1)
[2012-06-16 13:13] upgraded lib32-libpng (1.5.10-2 -> 1.5.11-1)
[2012-06-16 13:13] upgraded lib32-libx11 (1.4.99.902-1 -> 1.5.0-1)
[2012-06-16 13:13] upgraded lib32-nvidia-utils (295.53-1 -> 295.59-1)
[2012-06-16 13:13] upgraded lib32-sqlite3 (3.7.11-1 -> 3.7.13-1)
[2012-06-16 13:13] upgraded lib32-util-linux (2.21.1-1 -> 2.21.2-1)
[2012-06-16 13:13] upgraded lib32-xcb-util (0.3.8-1 -> 0.3.9-1)
[2012-06-16 13:13] upgraded wine (1.5.5-1 -> 1.5.6-1)
Currently returning to the old fstab entry once again gives the initial error code about the security mechanism being upgraded in kernal release x.x (it always seemed to change with each kernel change) though the shares seem to mount just fine. I've looked through the wiki, man pages on die.net and googled everything I can think of and I find a lot pages mentioning ntlmv errors with no solutions, many telling me that ntlmv and ntlmv2 are mount options, but nothing that gives me any indication on why I might be getting this error or how to go about looking for a solution.
I've looked through the pacman logs on both my desktop and my file server that I'm connecting to in an effort to determine what might have changed and I found that:
the smbclient had been upgraded on both machines so I tried downgrading back to version 3.6.5-2 but there was no change when rebooting.
I also found cifs-utils had been upgraded on the file server.  So I downgraded that as well to the previous version (5.4-1), rebooted both machines and I'm still getting the same invalid arguement error.
I've now gone back and upgraded to the most recent versions of the downgraded packages on each machine but I'm at a loss as to what my next steps should be.  Where do I go from here to track this down and determine if this is a bug or configuration error.  Is there a cleaner way of mounting these shares that I should be using instead of fstab?
Thank you.

I had the same issue. After upgrading kernel to 3.4.5 today the cifs share mounted with original fstab settings. I believe it was caused by this bug:
kernel changelog wrote:    The double delimiter check that allows a comma in the password parsing code is
    unconditional. We set "tmp_end" to the end of the string and we continue to
    check for double delimiter. In the case where the password doesn't contain a
    comma we end up setting tmp_end to NULL and eventually setting "options" to
    "end". This results in the premature termination of the options string and hence
    the values of UNCip and UNC are being set to NULL. This results in mount failure
    with "Connecting to DFS root not implemented yet" error.

Similar Messages

  • Mounting a network share via Applescript or Automator causes errors in MS Office apps

    If I connect a network share using an automated process, either using Applescript or Automator, though the share shows up on the Desktop and I can open it and view the various folders and files, MS Office apps including Powerpoint, Excel and Word are unable to open the files.   Each gives a slightly different error message.  In Excel, it looks like this:
    In Word, it's:
    In Powerpoint, it's:
    BUT, if I connect to the server share manually (using Cmnd-K in Finder), all files and folders are properly accessible.  I cannot see any differences between the shares connected by the two different means on the Desktop.  They have the same name, are the same size, etc.; in short, everything about them seems identical.  I even took screen shots of the Get Info page from one of them connected by the different methods:
    "home" connected by Automator:
    and connected manually:
    Does anyone have any ideas as to why this is happening or how to fix it?

    I had the same issue. After upgrading kernel to 3.4.5 today the cifs share mounted with original fstab settings. I believe it was caused by this bug:
    kernel changelog wrote:    The double delimiter check that allows a comma in the password parsing code is
        unconditional. We set "tmp_end" to the end of the string and we continue to
        check for double delimiter. In the case where the password doesn't contain a
        comma we end up setting tmp_end to NULL and eventually setting "options" to
        "end". This results in the premature termination of the options string and hence
        the values of UNCip and UNC are being set to NULL. This results in mount failure
        with "Connecting to DFS root not implemented yet" error.

  • Systemd failing to mount a network share

    I just installed systemd and I'm having some problems getting it to reliably mount the network shares I have listed in /etc/fstab.  In case it is relevant, I should note that I have opted to install systemd alongside the usual initscripts.  I've created two different Grub menu entries to select between the two systems during boot.
    The relevant fstab entries are as follows:
    //192.168.1.54/MP3z /mnt/MP3z/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
    //192.168.1.100/share /mnt/share/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
    //192.168.1.100/docs /mnt/docs/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
    This is what I've observed with respect to mount failures:
    The share at 192.168.1.54 mounts every time without fail.
    Usually, one of the other two shares at 192.168.1.100 will fail to mount while the second share at the same ip address will succeed.  Which of the two that fails is apparently random.
    Only very occasionally will both shares at 192.168.1.100 mount successfully.
    So far, I have never seen both of these shares fail to mount on the same test run.
    I have tried changing the order of the fstab entries but it doesn't seem to affect things.
    I've tried adding the "noauto" and "x-systemd.automount" options to my fstab entries.  This seems to make things work although with this setup I think the shares are mounted the first time they are browsed, not during starup.  With these mount options set, the system hangs on shutdown with either the messsage "Unset automount mnt-share.automount" or "Unset automout mnt-docs.automount".
    I thought perhaps that this is happening because my network connection isn't being started in time to mount the shares correctly.  Though, I thought systemd handled these sorts of dependencies without any explicit configuration required.  Perhaps this has something to do with the two shares being on the same host (192.168.1.100)?  I don't have any problems with the third share at 192.168.1.54.
    Can anyone shed some light?
    Last edited by battlepanic (2012-08-15 19:28:05)

    I had the same problem. While logged in as root, I can't use an alias or Cmd+K to connect to a server, but it works fine as any other user. I tried the link above and after reading the mount_afp man page, it describes two steps needed to mount a server. Here's what I had to put in Terminal to mount a share called Installers:
    The root account does not seem to be getting past the first step when using Cmd+K or an alias to a network share, although this worked in previous versions of OSX.
    This problem was not fixed in 10.7.1

  • Unable to mount a network share drive in mac os 10.7 when logged in as root

    I enabled the root account by entering sudo passwd root in the terminal window. Once the account was enabled successfully, I logged out from my admin account and logged in as root. I then attempted to mount a network share running on an Xserve and a Windows share but was unable to. I logged out as root and logged back in using my admin account and I was then able to mount both shares successfully.
    Is there a new Lion security feature that prevents the root account from mounting network shares? If so how can I get around it?
    Thanks for your help.

    I had the same problem. While logged in as root, I can't use an alias or Cmd+K to connect to a server, but it works fine as any other user. I tried the link above and after reading the mount_afp man page, it describes two steps needed to mount a server. Here's what I had to put in Terminal to mount a share called Installers:
    The root account does not seem to be getting past the first step when using Cmd+K or an alias to a network share, although this worked in previous versions of OSX.
    This problem was not fixed in 10.7.1

  • How Do I find out what app is auto-mounting a network share and stop it?

    I have a new laptop, the 13" rMBP.  I installed Steam and wanted to use the network share on my server to store the game files.  Everything went OK.  I closed Steam, disconnected the share and shutdown my laptop.  When I opened my laptop later on at work, it started to try and mount the network share.It keeps on going it.  I removed the Steam app and all files related to Steam that I could find.  I've looked at fstab, auto_home, auto_master and a large list of other files and directories and I *still* cannot find the offending file that's auto-mounting the share.  It's really frustrating.
    The share auto-mounts when I am home but not on the desktop or in finder.  I find it by looking at /Volumes/ in terminal.  If I mount the share manually under /Volumes/ it shows as Games-1 and mounts on the desktop under Games.
    Does anyone have any ideas on where I should be looking to find the offending process/file/daemon?
    Thank you!
    Trevor

    thanks for the reply but are you sure about this? What difference would it make? Why 5 apps?
    Even if it does work, which I doubt, at some point, I will have to resync ALL my apps again and surely the same thing will happen again, and I will be none the wiser. I still won't know which app it is. There must be a way of finding this out.
    Any ideas?
    What is really freaking me out is how it is connecting to my carrier (who is charging me) with Cellular data switched off.......?
    Thanks again.

  • Window 8.1 system unable to access network shares via VPN connection

    Is there something inherent to Windows 8.1 that prevents it from accessing shares on a domain?
    I know that it cannot join a domain, but does that also mean that it cannot access shares which are on a domain?
    My problem is that I have several user that are running windows 8.1 that are connecting to our network via a VPN.
    The users have domain accounts but their computers as windows 8.1 cannot joined to the domain.
    So to access network shares they have to use their domain credentials to create a VPN connection.
    Once connected the user can RDP to systems on the domain using their domain accounts, so I know that their user names/passwords and permissions are correct. They can access these systems using the computer name, so I don't feel that I have a DNS issue.
    They can see the shares on our file server, but when they try to access their departments shared file, they receive an access denied message. There are a few shares that are completely wide open, shared to all users and all departments but they cannot access
    those shares either.
    You can ping the file server, from the the client when they are connected to the VPN but you just cannot access any of the shares.
    So...
    I am thinking that it has something to do with windows 8.1 and not being able to join a domain, but I cannot find anything to explicitly support this thought.
    Other users running a variety different OS (windows 7, OSX, Linux) can all access the shares without any problems via the VPN, so I am a little stumped.

    I have done some more testing and oddly enough I can map a drive if I use the IPaddress, but not the computer name, when checking the check box "connect using different credentials"and providing they users domain credentials.
    This seems to point to a DNS issue, one would think, but I can hit the file share server by name \\fileserver.dev.lan
    I can see all the shares, so dns seems to be fine right?
    So I don't understand why I can map a drive using do the IPaddress and not the machine name, but yet I can see and ping the server by name?
    When I try to create a mapped drive by machine name I receive the following message:
    Windows cannot access \\fileserver.dev.lan\all
    You do not have permissions to access \\fileserver.dev.lan. contact your network administrator  to request access.
    But if I use the \\x.x.x.x\all using the very same user and password I get connected with no problem.
    This only seems to happen on windows 8.1, which leads me to think that has something to do with OS. 
    I am thinking about upgrading to windows 8.1 pro, but I don't want to go though the hassle and expanse is the OS is not the problem.

  • Kerberos tickets not used for mounting CIFS/SMB shares ( 10.5.3)

    Has there been an improvment since 10.5.3 for anyone regarding this ?
    For me, not.
    See this thread for the original topic:
    http://discussions.apple.com/message.jspa?messageID=6065277#6065277

    (just reposting this from a different mac discussion thread)
    OH THIS IS SO WRONG
    all the GUI techniques fail to use the TGT but using the COMMAND LINE WORKS OK. this includes SMB and AFP (our AFP service is kerberised)
    THIS WORKS
    mkdir /Volumes/manualmount
    mount_afp "afp://;AUTH=Client%20Krb%20v2@yourserver/volumename" /Volumes/manualvault
    BUT THIS DOESN'T
    "apple-k" (connect to server) -> prompts for name and password
    our workround then is that we are going to roll out leopard to our users with something like this in a login script to connect to one volume on our principal afp server. that way it appears in the sidebar AND once the server trusts the client they can connect to the other volumes for free.
    this is far from satisfactory, but it is simple from the user's perspective.
    now if we can only get the loginwindow to prompt when a password is due to expire

  • [SOLVED] LibreOffice and Network Shares via Gigolo

    My work desktop mounts shares in Active Directory using Gigolo. I am able to mount, browse and generally be at peace with the world with this setup with Thunar and Nautilus, and everything else (eg, gedit).
    For some reason, LibreOffice refuses to show any of the network mounts. When I try and save a document, the mounted shares just aren't there. I would expect them to show under "My Documents" in the left of this [img]screenshot[/img].
    Browsing to ~/.gvfs/ doesn't display anything either.
    If I try and open a file from any of the shares by double-clicking them in Thunar/Nautilus then I get the LibreOffice splash screen and then nothing. The main window doesn't open and the process terminates.
    Any ideas folks?
    Last edited by fukawi2 (2013-11-18 22:16:22)

    Well that's embarressing that it was that easy. That makes the whole thing look much better too. I had no idea there was a split of a separate Gnome package, but looking at the wiki it doesn't appear to be mentioned anywhere other than for making everything look nicer. I might fix that up.
    Thanks Awebb   +50 internets for you.

  • Client Network Shares Via RWA

    How can I add client shares to the remote web access as described here: 
    http://jpd.ms/network-drives-on-sbs-2011-remote-web-folders/
    I have tried the suggested actions. That being:
    "On your SBS server navigate to C:\Program Files\Windows Small Business Server\Bin\RemoteAccess.  Locate and BACKUP a
    file named web.config.  Open the file up in notepad, just drag it in.  Search for;
    <wssg.storageProvider type=”Microsoft.WindowsServerSolutions.Web.Storage.SBSStorageProvider, Wssg.Web.StorageProvider” />
    Comment this line out by adding <!—- and —-> respectively;
    <!—- <wssg.storageProvider type=”Microsoft.WindowsServerSolutions.Web.Storage.SBSStorageProvider, Wssg.Web.StorageProvider” /> —->
    Now directly below that line add the following;
    <wssg.storageProvider type=”Microsoft.WindowsServerSolutions.Web.Storage.FileSystemBasedStorageInformationProvider, Wssg.Web.Internal” shares=”\\fileserver\Share1;\\fileserver2\Share2″ />
    Obviously replace \\filesever\share1, etc with the UNC for your shares.  Once you do this run an iisreset or just reboot.  Test and enjoy."
    I am now getting the "Gadget failed to load" error. Does anyone know what changed from 2011 to 2012?

    Hi,
    Based on your description, did you mean that make specific users to access specific folder in RWA? Sorry, I’m
    a little confused with your problem. If anything I misunderstand, please don’t hesitate to let me know.
    If make specific users to access specific folder in RWA, please open Dashboard and navigate to STORAGE. In
    Server Folders tab, please select Add a folder task to add folders. In Add a Folder wizard, if want to store the folder in another location (not locally), you can click “Browse…” button to select other locations on other servers. Then configure correct
    permission for specific users to access this folder in the Add a Folder wizard.
    Then, specific users (and administrator) will be able to access the specific folder in the RWA.
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • How can I stop an network share from auto mounting?

    I have a recent 13" MBPr and I installed Steam.  For kicks, I told it to save the library on my 10.8 mac mini server.  This worked well.  It worked so well, I started up Parallels and did the same thing for my steam library on my boot camp partition. I closed Parallels and Steam then put my laptop to sleep.  I was away from my home network and repeatedly received messages about not being able to access my server in a standard Finder pop-up.  No big deal, I opened Steam to try and remove the library from my list.  It was no longer listed.
    Upon arriving home I opened steam and still could not find my share in the list.  I removed Steam and all it's support files.  Still on every boot I get the finder error about not being able to connect to my server.  When I boot up my parallels boot camp VM I get the same Finder error.  It pops up several (I never bothered to count) before it stops after I keep closing the pop-up.
    I've looked at /etc/auto_master and /etc/auto_home, my login items, and I cannot find the process that keeps trying to mount the network share.  When I am at my home and reboot my mac or boot parallels I do not receive the error.  But I also do not see the mounted share on my desktop.  I do see it when I perform the ls command on /Volumes.  When I try and cd into it I get a Permission Denied error.  Root/Wheel seems to own the mounted share.  When I sudo the folder I see all the files stored on that volume.
    Does anyone know how I can stop this from happening without resorting to creating a new user?  I just got this one the way I like it (before I screwed it up with steam!)
    Thanks for reading my short novel.

    did the restore through itunes but to no avail.
    Then you must have restored and installed your backup when requested.  To remove those emails, you have to restore as new, i.e. without your backup, as roaminggnome suggested.

  • How to mount network share on lion permanently

    I want to know how to mount a network share from my NAS on mountian lion.
    I have seen and tried the suggestions about using command+k or the "go connect to server" and mounting that way so the password for the share is put into the keychain, then dragging the now mounted share to the system preferences user login items.
    However this isn't satisfactory. It causes windows to pop up for each share that I have when logging in.
    What I Want is for the share to appear as a mounted hard drive in the left navigation column of the finder window. I'd also like to be able to make a shortcut to the share on my desktop (or put it in my dock bar). If it shows up under devices that is perfection okay too, just so it's there somewhere logical.
    The pop up windows simply clutter up the desktop, and if they are closed, then the share is closed too, and then there is a manual process of having to use the very tedious command+k or go connect to server method to connect again.
    I need them to be able to click and open the share. I don't need them wasting time putting in share paswords and the link over and over.. the share should just be there for them as they work through the day. And if they close the folder/window, then it should be easy to get back to it.
    This is possible on windows and I want these mounts to work the same way.
    note: my NAS uses smb

    That should work. You could try deleting the passwords in Keychain associated with it and try it again.
    Another route: Create Applescript:
    Select the network drive and get info on it. Copy the server address. Open up Applescript Editor in the Utilities folder and create a new script. Type in mount volume, add space, "paste server address within quotations", and save as application to your documents. Run it from within applescript editor to verify it works. When it asks for a passwork, save it in Keychain.
    Under system preferences/accounts/login items, click the + sign to add and select the saved application.

  • Finder crashes when trying to connect to network share

    Hi!
    I've just upgraded my Mid 2012 MacBook Pro to Mavericks, and found that Finder always crashes when trying to connect to my office network share via an IPSec VPN connection. It's a Synology DiskStation NAS, so i have the options to connect via AFP or SMB, however both result in the same, the crashing of finder. Even after i relaunch it, i can't open finder, and can't even shut down or restart my system (only by holding the power button for 5 secs...)
    At first i thought it's the result of the latest Little Snitch version, but the problem remained after completely removing Little Snitch.
    Unfortunalely i won't be able to try connecting to the NAS on the local network until monday, but i'd really appreciate if someone could point me to the direction of some solution as this way i can't do any of my work.

    Just a quick heads up. I finally managed to resolve the issue. It seems that mavericks doesn't handle the MTU of the vpn connection correctly, so i ended up modifying the MTU on the VPN gateway.

  • Windows 7 - Files missing from network share after trying to burn and no data cached to be burned

    I ran into an issue trying to burn some file from a network share using Windows 7 Home Professional.  I was trying to burn some .jpg files from a mapped network share drive using explorer.  Every time I would drag the files to be burned from
    the share drive to the explorer screen to be burned, the files would disappear from the share.  To make things worse the files would not show up in the screen to be burned.  I was unable to locate any of the files on either of the systems when performing
    a search after this took place.  I verified that the steps that I was taking to burn the files were the same as outlined on the Microsoft site.  No matter what I did to burn these files, they were deleted from the mapped network drive. 
    Below are the steps that I took that both resulted in the files being deleted as well as what I had to do to finally burn the disc.
    Steps that resulted in files being deleted:
    1. Insert blank CD into drive. 
    2. From prompt select burn using explorer (Mastered Format)
    3. Enter title and select with CD/DVD, click Next.
    4. Open a second explorer window, navigate to mapped network drive with files to be burned and snap next to explorer to be burned.
    5. Drag and drop the files from the share drive to CD.
    This where the train would fall off the tracks every time.  I would receive a message that the file(s) no longer exist and if I wanted to continue.  From here the files would be deleted from the share drive.  The best part is that the files
    would also NOT be locally stored to be burned. 
    Steps to burn share files WITHOUT delete:
    Follow steps outlined above, but instead of just dragging and dropping the files as outlined in step 5 select the files from the network share location, right mouse select copy.  Then right mouse select paste in the explorer window to be burned.
    I have tested this many times and every time ended up with the same problem.  At this point I am sure that there is a problem with the way that Windows 7 is performing the burn.  The system that I was using to burn is Windows 7 Home Professional
    with all the patches and updates loaded.  The remote system is Windows XP Professional with all the patches and updates loaded.
    Thanks in advance

    Yes, the problem is still continuing. However, after looking into as much of it as I can, I can confirm something that r.p.b_ started stumbling on. The files are deleted IF AND ONLY IF a user is using the built-in Windows 7 disc burning utility AND is dragging
    and dropping the files to the drive from a network share; this doesn't happen locally. If you watch what happens in the native folder, the files are literally scrubbed from the drive as they are processed and added to the image. However, if you Right Click
    on the files and copy them, then Right Click->Paste onto the drive, they remain. (The keyboard shortcuts also worked.) Also, 3rd party disc burning utilities function they way the should. (In other words, they don't delete the files.)
    My speculation is that there's a bug in the coding that sees the network share as a temporary buffer file while the image is being prepared. Then, as the files are processed in what ever way is needed, the "temporary buffer" is being deleted. The result:
    lost files on a network share. But, this is just speculation.

  • Problems with mount and unmount of network shares

    Hi,
    I use an Apple script to mount four network shares during startup of an OS 10.4.4 Powerbook. Unfortunately it seems that Tiger can't always mount them all. Sometimes it only mounts three of them, but pressing Command + K indicates that the fourth is already mounted because it's grayed out. How come I can't see it on neither the desktop nor the favorites list in a Finder window then?
    I have a Tiger installation at home with Ciscos VPN Client 4.8 installed. I use that VPN client to gain access to the company's network. When the connection is established, I mount a share (with AFP over TCP/IP) on the company's server running Win2003 and ExtremeZ-IP.
    When I close down Ciscos VPN Client, the mounted network share doesn't unmount automatically, and if I forget to toss that network drive in the trash before closing down or restarting my Mac, it hangs. Why can't it just unmount that drive automatically when the VPN connection is gone?
    Regards
    Thomas G. Madsen
    Powermac G5 (2 x 1.8 Ghz)   Mac OS X (10.4.4)  

    This may happens because broadcasts do not go through an IPSec tunnel.
    Browsing Network Neighborhood is a function of the Microsoft browsing service. Any problems are usually because the PC or master browsers do not function properly. Network Neighborhood is officially not supported. However, it works if configured correctly. Browsing Network Neighborhood works by obtaining the browse list from either a master or backup browser. This list is obtained locally on your LAN by using NetBIOS Broadcasts to locate domain browsers.
    Inorder to resove this :
    Make sure you have NetBIOS over TCP enabled on the adapter that you use to connect to the domain.
    Refer this related links:
    http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_tech_note09186a0080194b4a.shtml

  • Can you use a network share as location for users' home

    I am running a Mac mini with Mountain Lion and Server.app as a home server. For added storage space I have a NAS. I would like to set up the open directory network users' home share on the NAS. Is that even possible?
    I am able to mount the network share on the mini using either afp or nfs, and I can also add the NAS share as a home folder enabled share in the server.app and select that as location for a users home folder, but that only results in the user not being able to log on to his account. Is there something that I am missing or is what I am trying to accomplish simply not possible?

    It used to be officially supported to use NFS for clients to access their network home directories but with Lion (and Mountain Lion) this was no longer officially supported.
    Therefore the need as I mentioned to 're-share' the volume via AFP. As you implied this does unfortunately impose an additional network overhead as traffic has to go as follows.
    client ----> AFP ----> Server -----> NFS -----> NAS
    What you could consider to help at least a little bit is to connect the server to the NAS on a totally separate network to the network the server uses to talk to the clients on. The main network would be between the server and clients, and you would use a second Ethernet connection just link the NAS and the server. As the clients will not need to talk directly to the NAS this will not be a problem. This would at least mean that each network only gets one set of traffic either AFP or NFS but not both and means the server can use both at full speed at the same time.
    The Mac Pro still has two built-in 1Gbps Ethernet ports but you can also get either a USB3 Ethernet adaptor or a Thunderbolt to Ethernet adaptor (I have used one of these on a Mac mini server).
    If you did not already have the NAS then people starting from new would be better off either getting a Thunderbolt RAID which can be directly attached to the Mac server, or at the higher-end go the traditional route of setting up a SAN and using an FDDI connection.
    Note: You can now get Thunderbolt to FDDI interfaces.

Maybe you are looking for