Mounting SBS2011 C:/ Share

I am trying to mount a Windows SBS2011 Share but I am repeatedly getting:
mount error(13): Permission denied
I have tried many things but all result in the same error. I definitively have permission to access the drive.
I have tried the below and many variations of the below:
#mount -t cifs //SBS2011/C\$ /mnt/network -o user=Lerp,password=<redacted>,sec=ntlm
#mount -t cifs //SBS2011/C\$ /mnt/network -o user=Lerp,password=<redacted>,ip=192.168.0.10,sec=ntlm
#mount -t cifs //192.168.0.10/C\$ /mnt/network -o user=Lerp,password=<redacted>,sec=ntlm
#mount -t cifs //192.168.0.10/C\$ /mnt/network -o user=192.168.0.10/Lerp,password=<redacted>,sec=ntlm
Here's the results of smbtree:
MM
\\SBS2011
\\SBS2011\UserShares
\\SBS2011\Users
\\SBS2011\Technical
\\SBS2011\SYSVOL Logon server share
\\SBS2011\SHARP MX-M314N PCL6 SHARP MX-M314N PCL6
\\SBS2011\SHARP MX-M314N SHARP MX-3140N PCL6
\\SBS2011\RedirectedFolders
\\SBS2011\Public
\\SBS2011\print$ Printer Drivers
\\SBS2011\NETLOGON Logon server share
\\SBS2011\IPC$ Remote IPC
\\SBS2011\GroupMetrics MailTips group metrics publishing point
\\SBS2011\F$ Default share
\\SBS2011\E$ Default share
\\SBS2011\Drivers$
\\SBS2011\Designjet 500-24 HP Designjet 500 24 by HP
\\SBS2011\Cert
\\SBS2011\C$ Default share
\\SBS2011\ADMIN$ Remote Admin
\\SBS2011\Address "Access to address objects"
\\SBS2011\actsql
\\SBS2011\Accounts
\\PURCHASING
\\ORDERPRINT
\\DESIGN3
\\DESIGN1
and for smbclient -L SBS2011
Domain=[MM] OS=[Windows Small Business Server 2011 Standard 7600] Server=[Windows Small Business Server 2011 Standard 6.1]
Sharename Type Comment
Accounts Disk
actsql Disk
Address Disk "Access to address objects"
ADMIN$ Disk Remote Admin
C$ Disk Default share
Cert Disk
Designjet 500-24 Printer HP Designjet 500 24 by HP
Drivers$ Disk
E$ Disk Default share
ExchangeOAB Disk OAB Distribution share
F$ Disk Default share
GroupMetrics Disk MailTips group metrics publishing point
IPC$ IPC Remote IPC
IRS Disk
Line100 Disk
NETLOGON Disk Logon server share
print$ Disk Printer Drivers
Public Disk
RedirectedFolders Disk
SHARP MX-M314N Printer SHARP MX-3140N PCL6
SHARP MX-M314N PCL6 Printer SHARP MX-M314N PCL6
SYSVOL Disk Logon server share
Technical Disk
Users Disk
UserShares Disk
Domain=[MM] OS=[Windows Small Business Server 2011 Standard 7600] Server=[Windows Small Business Server 2011 Standard 6.1]
Server Comment
Workgroup Master

Hi Lepr do you have rights to mount in /mnt ?
The following works great for me in my /etc/fstab .
//192.168.1.2/Data /home/xaris/data cifs username=xaris, password=MyPass, iocharset=utf8, dir_mode=0777, file_mode=0777 0 0

Similar Messages

How to allow users to mount a Samba shares on a WXP

Through lots of reading I've managed to get an understanding of how to mount SMB shares at bootup by placing the proper edits in /etc/fstab. While having the shares of the server, running Contribs.org SME Server 6.01 (recently known as Mitel SME Server) and acting as a samba server, being mounted at startup is perfect since the server is always on. This is not the best idea for the XP workstation since it isn't always on. Here is a copy of my present fstab file with x's replacing the passwords.
fstab [B---] 0 L:[ 1+19 20/ 21] *(1085/1086b)= . 10 0x0A
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
sysfs /sys sysfs defaults 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat user,noauto,unhide 0 0
//192.168.2.2/stuff /mnt/silicon2 smbfs username=kingnubian,password=xxxxxxx,user
//192.168.2.105/e-smith /mnt/silicon1 smbfs username=kingnubian,password=xxxxxxx,users,noauto
/dev/discs/disc0/part5 swap swap defaults 0 0
/dev/discs/disc0/part1 / xfs defaults 0 1
I would like users with an account on the Linux box to mount the remote share on the XP box without needing to SU and consequently need the root password. When trying now to mount "e-smith" (The share on the XP box) as a user using "mount /mnt/silicon1" I get a message about needing to be SU.

To allow users to mount smb shares you need to make smbmnt suid:
# chmod +s /usr/bin/smbmnt
Note however that the user needs to own the directory used as mountpoint. So I don't know how to make 'mount /mnt/silicon1' in your setup work for all users.
For the users to be able to unmount the smb shares as well you need:
# chmod +s /usr/bin/smbumount
Now users can do 'smbmount //server/share mountpoint -o username=whatever' or simply 'mount mountpoint' if the details are specified in fstab. To unmount root can do 'umount mountpoint' or users can do 'smbumount mountpoint'.
Don't confuse smbmount with smbmnt - the first is the command you use to mount shares manually, the second is the one that should be suid and is used both by smbmount and by mount -t smb.
Hope this helps.
-bogomipz

Cannot mount multiple CIFS shares in /home

I have 2 users, Joe and Fred, who each have their own directory in /home. I also have a Netapp filer with a CIFS share called CorpData, which has subdirectories for Joe and Fred.
On the Arch Linux box, I have this for my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1
UUID=d93def89-7611-43c8-a74f-e20bee64bd7e / ext4 rw,relatime 0 1
//10.1.1.141/CorpData/joe /home/joe cifs credentials=/etc/credentials,noserverino,_netdev,uid=joe,gid=users 0 0
//10.1.1.141/CorpData/fred /home/fred cifs credentials=/etc/credentials,noserverino,_netdev,uid=fred,gid=users 0 0
The problem is that at boot time, Joe's directory will be mounted, but Fred's will not. The reverse is true if I reverse the two entries in fstab.
If I issue the "mount -a" command after logging in, the second mount does get mounted, but also generates this error message:
mount error(16): Device or resource busy
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
I did refer to man mount, but since only the second mount is failing, I don't know what I could try differently. There are many more directories in CorpData, so I don't want to just mount that entire share on /home.

Looking into this further, it seems that the server is not able to accept the second request so quickly after the first. Is there any way to insert a delay or sleep command between the two mount entries in fstab?

How can a mount a NFS share exported from OpenBSD?

Hello Apple Discussions:
I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
http://www.bsdforums.org/forums/showthread.php?t=54308
Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
ON THE OPENBSD BOX:
#/etc/exports
/fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
/exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
#/etc/hosts.deny
ALL: ALL
#/etc/hosts.allow
ALL: 192.168.222.233 192.168.222.253
#/etc/rc.conf.local
portmap=YES
lockd=YES
nfs_server=YES
#here's proof that the daemons are running on the OpenBSD box;
rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 863 mountd
100005 3 udp 863 mountd
100005 1 tcp 613 mountd
100005 3 tcp 613 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 895 nlockmgr
100021 3 udp 895 nlockmgr
100021 1 tcp 706 nlockmgr
100021 3 tcp 706 nlockmgr
# actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
ON THE TIGER SERVER:
# here's proof that tiger server sees the mounts:
showmount -e 192.168.222.111
Exports list on 192.168.222.111:
/fives 192.168.222.0
/exports/fives 192.168.222.233 192.168.222.253
# here's the result of user fives' attempt at mounting a share:
sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
mount_nfs: /imports/fives: Permission denied
# yet user fives has no problem mounting same share on linuxppc box.
What is different about OSX server? I thought it was supposed to speak NFS?
---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
Each user is free to choose which of those tracks they want in their library.
There is an Apple help article on multiple users.
http://docs.info.apple.com/article.html?artnum=300432

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.

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

Mount error when mounting Windows Server share

Trying to mount a share on a Windows Server I have in my home.
When I use:
smbclient -L SERVERNAME -U administrator
and I enter the password after the prompt
It returns a list of all the shares in the server like so:
Domain=[SERVERNAME] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Sharename Type Comment
SHARE1 Disk Shared folder
SHARE2 Disk Shared folder
SHARE3 Disk Shared folder
Domain=[SERVERNAME] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Server Comment
Workgroup Master
but when I try to mount of the shares with
# mount -t cifs //SERVERNAME/SHARE1 /mnt/mountpoint -o user=administrator,password=password
it returns an error
mount error: could not resolve address for SERVERNAME: Unknown error
Am I doing something wrong?
Thanks,

the SERVERNAME in these commands is a netbiosname and can differ from the hostname.
Smbclient seems to use it's own method to resolve netbiosnames, possibly the mount command uses a different method.
Try the mount command with the ip-address of the server instead of SERVERNAME to verify mounting the share works.
If the share can be mounted by //ip-address/SHARE1 , you may need additional options for the mount command to make netbios name resolution work correctly.
check man mount.cifs .
edit : typo's
Last edited by Lone_Wolf (2013-08-10 12:40:47)

How can I mount an SMB share in the Finder? (Leopard)

In Tiger, I was able to mount a SMB share in the finder and it would be displayed under the "Devices" section. With Leopard, I cant get this to work. Leopard is much easier to browse network shares on my Windows machine under the "Shared" section, but I would still like to have certain folder mounted all the time, preferably on startup.

Works perfectly for me, so let me make sure we're on the same page.
I mount the volume manually, using Connect to Server.
I drag the volume, now appearing in Computer and on the Desktop, to the Devices section of the Sidebar.
I eject the volume, and it disappears from the Sidebar.
I mount the volume again (it could be by browsing for it, through Connect to Server, or through an Automount Maker document)
It appears, without my having to do anything, in the Sidebar.
As far as I can tell, this is what you were aiming for. Am I missing something?

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

Proper way to mount a fat32 share

I've seen so many different ways to mount my windows share in fstab with various (to no) options - users, async, dev, etc.
Problem:
My Documents, My Pictures, and all those other My directories will have the root write permission flag stripped in linux when I boot back and forth. As best I can tell, any of those window directories which have a unique picture icon embedded in them will change that root level write flag. If in XP, I keep those directories with a normal folder icon, the w flag will be persistent between boots.
Anyone else have this problem? If not, all I want to do is r/w and have normal user mount the fat32 share. Can somebody help me with the fstab entry?

Thanks, lucke. Works great.
I'm still having problems with mounting options I think, or Windows XP in general. Here's the icon/permission dilemna:
skoal@morpheus:///mnt/windows/My Documents $ ls -ald My\ *
dr-xr-xr-x 7 root users 16384 2007-09-02 15:12 My Backups
dr-xr-xr-x 9 root users 16384 2007-09-02 15:20 My Downloads
drwxrwxr-x 3 root users 16384 2007-05-17 06:18 My Games
dr-xr-xr-x 6 root users 16384 2007-09-02 15:15 My Music
dr-xr-xr-x 5 root users 16384 2007-09-02 15:15 My Pictures
dr-xr-xr-x 2 root users 16384 2007-09-02 15:09 My Received Files
drwxrwxr-x 6 root users 16384 2007-07-15 16:50 My Videos
skoal@morpheus:///mnt/windows/My Documents $ touch hello
touch: cannot touch `hello': Permission denied
skoal@morpheus:///mnt/windows/My Documents $ cd My\ Pictures/
skoal@morpheus:///mnt/windows/My Documents/My Pictures $ touch hello
touch: cannot touch `hello': Permission denied
1. Strangely enough, as root I can r/w to even directories marked with w- on them, like My Downloads for example.
2. However, as skoal, I cannot.
3. When I change permissions on w- flagged paths to w+, chmod 775 My\ Downloads, it will work for skoal (in that folder).
4. But from 3, when I go back to XP, the system icons for those My folders marked with w+ will have a missing icon now. And I have to rerun "rundll32 mydocs.dll,PerlUserInit" to get them back.
Any ideas?

Mounting an NFS share

Hi,
I'm attempting to mount an NFS share and having no success. Regardless of the settings I try, the Finder still denies me access to the NFS share, even though it mounts fine. I seem to have no read or write access to the share.
I've tried exporting the share (in /etc/exports on the server machine) in two ways: with
/home/REDACTED/share REDACTED/28(rw,sync,all_squash)
And
/home/REDACTED/share REDACTED/28(rw,sync,insecure,all_squash,anonuid=1001,anongid=1001)
In the second example, the anonuid and anongid are those of the shared folder's owner and group. I added "insecure" because a how-to on the web claims that OS X won't work with any shares that don't have this specified.
With either of these settings applied, Disk Utility verifies the existence of the share, and mounts it. However, I can neither read files within, or add files to, the shared folder. The error produced is:
The folder “share” can’t be opened because you don’t have permission to see its contents.
I have tried the following Advanced Mount Parameters, each to no effect:
nodev resvport nolocks locallocks intr soft wsize=32768 rsize=3276
nodev nosuid resvport nolocks locallocks intr soft wsize=32768 rsize=3276 ro
nodev,nosuid,resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
nodev,nosuid,resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276 ro
resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
-i,-s,-w=32768,-r32768
-P
I'd rather not employ SAMBA, and the Apple File Sharing package for my server's OS (Ubuntu 11.10) appears to be bugged currently. Besides, NFS would be a far neater solution.
Any helpful advice?
S.

Scotch_Brawth wrote:
I've simply come at NFS as being the most appropriate file-sharing implementation for my needs - it supports automatic mounting at boot using tech native to both my Linux OS and OS X.
That is part of the problem. NFS is designed for environments where all servers are mounted (by root) at boot time and permissions are managed via NIS or LDAP. That is the default setting. If you are using something else, it requires some hacking.
I've had SAMBA working in the past, but I guess a certain air of contamination creeps in when using a Windows protocol to allow interaction between two UNIXy systems.
Plus, you would now have two different 3rd party reverse-engineered reimplementations of a foreign protocol.
AFP would be great, but despite receiving support on the Ubuntu forums and IRC, I failed to get it to work - it may be bugged; which would not be surprising, as 11.10 (with Kernel 3) has proved problematic in several other ways.
Perhaps Ubuntu is targeted more towards desktop rather than server usage. About the time I last played with NFS, I also played with Netatalk - with disastrous results. Supposedly Netatalk is better now. It's authors would be more than happy to sell you a support package.
I did use the default settings - they failed to allow a working NFS share. I then applied the variety of settings as recommended by apparently knowledgeable people. Still no success. I have read that UID/GID settings are an important aspect of NFS, but the issue in this case (as far as I understand it) is that all UID/GIDs below 1000 are privileged in Ubuntu 11.10, whilst on OS X these are below 501. So, the choice is either to give the shared folder owner a privileged UID/GID pair, or change the UID/GID of my Mac users to meet the NFS servers needs - not something I'm happy to do for so small a gain.
You can create a throwaway account on the Mac and just reset the GID/UID to values equal to an account on the Linux machine. That would establish that it is properly working in the default configuration. Then you could edit /etc/idmapd.conf.
For that reason, I use the "all_squash" option, because the share in question is not for anything remotely critical and the data to be transferred and stored is both worthless and transitory.
Since all_squash maps everything to nobody, you would have to hack up the permissions on the server to make everything world writeable. I think it will work with /etc/idmapd.conf and without all_squash.
I know nothing about NFS other than that its capabilities and integration meet my needs.
Just what are your needs? If the data is worthless and not critical then Netatalk might be the best option. If you can't get that to work, you could try MacFUSE on the Mac side and mount over sshfs. That is normally what I do. It isn't all that reliable, but you don't seem to require that.
What information I did find regarding OS X and NFS was that there were peculiarities that required certain settings to be present on the server and the client respectively - for example, OS X apparently requires "insecure" to be set as an option, or it simply won't connect properly. I don't know why, but I have no choice to trust to the advice of others in this case, until I have sufficient grasp to take care of the whole thing myself.
This goes back to the expectation that NFS expects to be always connected and mounted by root. Apple sells very few desktop machines anymore so it assumes a different, user-centered environment. You could use "insecure" on the server side to allow connections from "insecure" ports > 1024 that a regular users can connect with via the Finder. You could use the terminal with "sudo mount_nfs -o resvport" to tell the Mac to use the root user to connect via a secure port instead.
If you genuinely think you're able to help, then I'm happy to hear your advice. What would you recommend?
I appreciate your meeting me halfway. I think all you really need is /etc/idmapd.conf without all_squash. Then you could setup AutoFS and you could use NFS in a modern environment without even bothering to mount it.

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.

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.

How do I mount a Windows share on 10.5.3 server so everybody can use it?

I was successful in mounting a share and, I hope, giving it 777 directory permission and 666 file permission. However, nobody else can even see it! I used:
mkdir /share
mount_smbf //logname:password@windowsserver/share /share
This worked for me. I can see it and access it from a shell window. However, I want everybody else to be able to get to it.
I have the apple set up so it can be accessed from the windows machine but I keep coming up empty trying to go the other way.

I have the exact same problem dude - Sharename\Sub Folder\Sub Folder - therein lies problem. I can see the folder contents, if I logon to server as one of the users I can see them but if I connect via smb as the same user I cannot see them......

Slow Folder View When Mounting to Windows Share

I'm an intern at an educational institute and we have a graphics lab that has access to a large windows share. They use the share for storing large picture files primarily. Only individuals in certain classes have access to the drive and each student has their individual folder. Graphics shares this share with cad students so the share is called CADShare
On a windows machine when the student connects the only folder that is seen is their own which is folder name = 'firstname.lastname'
On a mac it seems to load every students folder within the share (around 400 students maybe?) and then pull every folder that it populated until the only one seen is the one you have permissions to. It will behave slightly different depending on the folder view.
If the folder is being viewed in list or detail view it will populate/unpopulate instantly and will cause the machine to 'hang' while it's doing this. But if the folder is in folder view it will only populate the full amount of folders. If you click on a folder that is supposed to be hidden it will then unpopulate that folder.
This is becoming an issue for students trying to save and access files in Adobe cs2 but it seems to be more of a problem with the finder than it is with Adobe.
Is there a way to change view settings to be more friendly to windows shares for it not to lag this much when viewing or has anyone seen anything like this?
Any thoughts or solutions would be helpful :]
Message was edited by: mcc_helpdesk

We've tried something similar to that, they actually connect using afp rather than smb?
But we've tried connecting:
afp://server/CADShare/firstname.lastname/
and
afp://server/CADShare/firstname.lastname/
It seems to connect to their share directly but it still mounts CADShare so when students browse for files through an application, for example the graphics students are using the "place" command, they experience that lag because of the volume of folders.
It seems like it might just be something our network guy should handle by either making each students folder an individual share or nesting the folders by class or instructor.
Thanks so far though, any other ideas?

Mounting SBS2011 C:/ Share

Similar Messages

Maybe you are looking for