mount -t cifs permission denied by mount -t smbfs works fine
I am having trouble mounting with cifs, but mounting the exact same command with smbfs works fine. The share is on another samba server and is set to full public guest access.
Last edited by jim mcnamara; 09-01-2009 at 04:03 PM..
Reason: code tags
Hi ,
I have a filesystem on AIX 4.3.3 which i need to share with other clients who use Windows NT and Redhat linux 7.3.
I use samba to share this with Windows NT Clients.
Now i was to share this with Linux clients.
When i try to nfs mount this on Linux i get
"mount: failed, reason given by... (1 Reply)
Hi,
- I have two solaris 10 servers. One is running nfs server (let's call it server-1) and has a share set through /etc/dfs/dfstab file:
share -F nfs /opt/SHARE (where SHARE directory contains sub-items that I want to share)
- On server-1, I have started the nfs server service and have... (2 Replies)
hi everyone
months ago i installed software on hp-ux box. So instead of going to the server room (which is far and cold :) ), I put the DVD in my windows xp box and mount it using CIFS, it was successful.
Now I want to install another software on the same hp-ux box using the same windows... (3 Replies)
I have two servers, 82 and 70.
My exports file on 82 reads
/ ...70(rw)
on 70 I have a mountpoint called mnt_for_82
I execute on 70
mount -t nfs -o rw ...82:/ mnt_for_82
I go to server 70 and indeed can read and travers the mounted subdirectories. However, I try... (0 Replies)
After switching from smbfs mount, the dmask/dir_mode and fmask/file_mode no longer have an effect on the newly created files. It seems to use the system umask instead.
I need the group to have write permissions without changing the root umask on the system. Any ideas?
example fstab:
... (0 Replies)
On Slackware14.0
Compiled cifs-utils with kerberos support
on request-key.conf added
create cifs.spnego * * /usr/sbin/cifs.upcall %k %d
But when i try
mount -o sec=krb5 -t cifs //SLACK64//Users /media/users
mount error(38): Function not implemented
Refer to the... (1 Reply)
Hello AIX gurus,
I am trying to mount a CIFS share on AIX and I could use some help. Here are the environment details:
AIX - 6100-05-01-1016
Domain Controller - WIN2K8R2 (authentication takes place here)
CIFS share is stored on a NetApp storage array that is joined to the domain
I have... (2 Replies)
I have a RHEL 5.7 system with a cifs mount from a Windows 2007 file server that I need to fix the permissions on. Once the share is mounted the permission for the mount are 777. I need to change that to 770 on the top level directory and to 640 on the sub-directory .ssh/. But when I run chmod... (0 Replies)
Hi,
I can't find any documentation of all available mount options of mount -v cifs
Unfortunately you can specify any fantasy options, no complains, and the mount command shows this option
In particular I want to know if there is a possibility to completely disable cifs caching in aix,... (3 Replies)
I have a Linux server with a cifsmount, the entry in /etc/fstab looks like this: //windows_server_name/xyz /opt/xyz cifs credentials=/etc/creds/xyz.creds,uid=abc,gid=abc,noserverino,directio,_netdev 0 0
The username and password are stored in /etc/creds/xyz.creds
This works fine.:wall: How... (1 Reply)
Discussion started by: Joke Holmer
1 Replies
LEARN ABOUT LINUX
cifs.upcall
CIFS.UPCALL(8) System Administration tools CIFS.UPCALL(8)NAME
cifs.upcall - Userspace upcall helper for Common Internet File System (CIFS)
SYNOPSIS
cifs.upcall [--trust-dns|-t] [--version|-v] [--legacy-uid|-l] [--krb5conf=/path/to/krb5.conf|-k /path/to/...] {keyid}
DESCRIPTION
This tool is part of the cifs-utils suite.
cifs.upcall is a userspace helper program for the linux CIFS client filesystem. There are a number of activities that the kernel cannot
easily do itself. This program is a callout program that does these things for the kernel and then returns the result.
cifs.upcall is generally intended to be run when the kernel calls request-key(8) for a particular key type. While it can be run directly
from the command-line, it's not generally intended to be run that way.
OPTIONS -c
This option is deprecated and is currently ignored.
--krb5conf=/path/to/krb5.conf|-k /path/to/krb5.conf
This option allows administrators to set an alternate location for the krb5.conf file that cifs.upcall will use.
--trust-dns|-t
With krb5 upcalls, the name used as the host portion of the service principal defaults to the hostname portion of the UNC. This option
allows the upcall program to reverse resolve the network address of the server in order to get the hostname.
This is less secure than not trusting DNS. When using this option, it's possible that an attacker could get control of DNS and trick
the client into mounting a different server altogether. It's preferable to instead add server principals to the KDC for every possible
hostname, but this option exists for cases where that isn't possible. The default is to not trust reverse hostname lookups in this
fashion.
--legacy-uid|-l
Traditionally, the kernel has sent only a single uid= parameter to the upcall for the SPNEGO upcall that's used to determine what
user's credential cache to use. This parameter is affected by the uid= mount option, which also governs the ownership of files on the
mount.
Newer kernels send a creduid= option as well, which contains what uid it thinks actually owns the credentials that it's looking for. At
mount time, this is generally set to the real uid of the user doing the mount. For multisession mounts, it's set to the fsuid of the
mount user. Set this option if you want cifs.upcall to use the older uid= parameter instead of the creduid= parameter.
--version|-v
Print version number and exit.
CONFIGURATION FOR KEYCTL
cifs.upcall is designed to be called from the kernel via the request-key callout program. This requires that request-key be told where and
how to call this program. The current cifs.upcall program handles two different key types:
cifs.spnego
This keytype is for retrieving kerberos session keys
dns_resolver
This key type is for resolving hostnames into IP addresses. Support for this key type may eventually be deprecated (see below).
To make this program useful for CIFS, you'll need to set up entries for them in request-key.conf(5). Here's an example of an entry for each
key type:
#OPERATION TYPE D C PROGRAM ARG1 ARG2...
#========= ============= = = ================================
create cifs.spnego * * /usr/sbin/cifs.upcall %k
create dns_resolver * * /usr/sbin/cifs.upcall %k
See request-key.conf(5) for more info on each field.
The keyutils package has also started including a dns_resolver handling program as well that is preferred over the one in cifs.upcall. If
you are using a keyutils version equal to or greater than 1.5, you should use key.dns_resolver to handle the dns_resolver keytype instead
of cifs.upcall. See key.dns_resolver(8) for more info.
SEE ALSO request-key.conf(5), mount.cifs(8), key.dns_resolver(8)AUTHOR
Igor Mammedov wrote the cifs.upcall program.
Jeff Layton authored this manpage.
The maintainer of the Linux CIFS VFS is Steve French.
The Linux CIFS Mailing list is the preferred place to ask questions regarding these programs.
cifs-utils 02/07/2010 CIFS.UPCALL(8)