Ok, it was unix, I updated it to ntfs
cifs-vf-01@irt-na06> qtree security /vol/media1 ntfs cifs-vf-01@irt-na06> Thu Sep 4 08:27:49 PDT [irt-na06:wafl.quota.sec.change:notice]: security style for /vol/media1/ changed from unix to ntfs
I still get the same “write protected” error when attempting to copy to the remapped drive
Should I re-run cifs setup? I want the simplest non-AD (since only one (service type) account will be accessing this share)
(1) Active Directory domain authentication (Active Directory domains only) (2) Windows NT 4 domain authentication (Windows NT or Active Directory domains) (3) Windows Workgroup authentication using the filer's local user accounts (4) /etc/passwd and/or NIS/LDAP authentication
thanks
On Sep 4, 2014, at 5:10 AM, Jordan Slingerland Jordan.Slingerland@independenthealth.com wrote:
Check the security style on the qtree with the “qtree status” command.
If it is unix, you will want to change it to ntfs.
--Jordan
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrei Sent: Thursday, September 04, 2014 2:32 AM To: Fletcher Cocquyt Cc: toasters@teaparty.net Lists Subject: Re: First time CIFS setup
I can think of two points. If you are using /etc/passwd or LDAP authentication for CIFS, it requires insecure protocol from client which is disabled by default since long time. Second - you need to have working windows-Unix user mapping. Usually there is default fallback user called "pcuser" which is entered in local /etc/passwd when CIFS is setup. If you are using e.g. LDAP, you need to ensure this use exists (or change default user or setup explicit mapping).
Отправлено с iPhone
04 сент. 2014 г., в 7:36, "Fletcher Cocquyt" fcocquyt@stanford.edu написал(а):
We are an NFS via vfilers shop, but had our first client request for a CIFS share.
I’ve setup a CIFS vfiler using the local account/password option.
cifs-vf-01@irt-na06> cifs shares Name Mount Point Description HOME /vol/media1/home Default Share everyone / Full Control
We can map the share, but get “the disk is write protected” when attempting a copy to the mapped drive.
The error the client receives when trying to map the drive is "The account is not authorized to log in from this station”
I’d like to resolve both our “write protected” and the client’s “not authorized” errors - why are these errors if the HOME share is created as “everyone / Full Control” ?
Any advice/links appreciated
thanks, Fletcher. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters