Hi Justin,
Yes, I did activate v3-ms-dos-client and deactivated enabe-ejukebox and v3-connection-drop:
::*> vserver nfs show -vserver XXXXXXX -fields enable-ejukebox,v3-connection-drop,v3-ms-dos-client
vserver enable-ejukebox v3-connection-drop v3-ms-dos-client
------- --------------- ------------------ ----------------
XXXXXXX false disabled enabled
Here’s the export policy:
::*> vserver export-policy rule show -vserver XXXXXX -policyname XXXXXX -instance
Vserver: XXXXXX
Policy Name: XXXXXX
Rule Index: 1
Access Protocol: nfs
List of Client Match Hostnames, IP Addresses, Netgroups, or Domains: 22.22.22.22
RO Access Rule: any
RW Access Rule: any
User ID To Which Anonymous Users Are Mapped: 0
Superuser Security Types: any
Honor SetUID Bits in SETATTR: true
Allow Creation of Devices: true
NTFS Unix Security Options: fail
Vserver NTFS Unix Security Options: use_export_policy
Change Ownership Mode: restricted
Vserver Change Ownership Mode: use_export_policy
Here’s the file-directory show output of the base volume itself:
::*> vserver security file-directory show -vserver XXXXXX -path /VOLUME
Vserver: XXXXXX
File Path: /VOLUME
File Inode Number: 64
Security Style: unix
Effective Style: unix
DOS Attributes: 10
DOS Attributes in Text: ----D---
Expanded Dos Attributes: -
UNIX User Id: 0
UNIX Group Id: 0
UNIX Mode Bits: 755
UNIX Mode Bits in Text: rwxr-xr-x
ACLs: -
And here it is for the directory I’m trying to rename:
::*> vserver security file-directory show -vserver XXXXXX -path /VOLUME/test
Vserver: XXXXXX
File Path: /VOLUME/test
File Inode Number: 22620
Security Style: unix
Effective Style: unix
DOS Attributes: 10
DOS Attributes in Text: ----D---
Expanded Dos Attributes: -
UNIX User Id: 0
UNIX Group Id: 0
UNIX Mode Bits: 755
UNIX Mode Bits in Text: rwxr-xr-x
ACLs: -
Thanks,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Parisi, Justin [mailto:Justin.Parisi@netapp.com]
Gesendet: Freitag, 7. April 2017 15:41
An: Alexander Griesser <AGriesser@anexia-it.com>; toasters@teaparty.net
Betreff: RE: Windows NFS Client + cDOT
Did you make the modifications mentioned in the TR to the NFS options?
Also, what does your export policy rule look like?
What does “vserver security file-directory show” give you for the newly created file? Who is the owner/what are the perms?
From: Alexander Griesser [mailto:AGriesser@anexia-it.com]
Sent: Friday, April 7, 2017 5:35 AM
To: Parisi, Justin <Justin.Parisi@netapp.com>;
toasters@teaparty.net
Subject: AW: Windows NFS Client + cDOT
Hi Justin,
I think I fired too early – one more thing just popped up.
I’ve set the registry keys for AnonymousUID and AnonymosGID to 0 each and am now able to write to that volume.
It’s mounted using NFSv3 currently:
Local Remote Properties
-------------------------------------------------------------------------------
z:
\\22.22.222.222\volnXXXXXXX UID=0, GID=0
rsize=65536, wsize=65536
mount=hard, timeout=0.8
retry=1, locking=yes
fileaccess=755, lang=ANSI
casesensitive=yes
sec=sys
I can copy files to this volume, I can delete files, traverse folders, etc.
But I – for whatever reason – cannot rename files. When I try to rename a folder, I get:
On the command line, a different error (Access denied) is given:
Z:\>move test test1
Access is denied.
0 dir(s) moved.
Z:\>ren test test1
Access is denied.
Any idea what I’m missing here now?
Thanks,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Alexander Griesser
Gesendet: Donnerstag, 6. April 2017 19:36
An: 'Parisi, Justin' <Justin.Parisi@netapp.com>;
toasters@teaparty.net
Betreff: AW: Windows NFS Client + cDOT
Hi Justin,
many thanks for pointing me there – I was still thinking pre 8.3 where this was not possible.
::> vserver nfs modify -vserver VSERVERNAME -v3-ms-dos-client enabled
was all it needed and I could successfully mount the share on a Windows Server 2016 now.
Best,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Parisi, Justin [mailto:Justin.Parisi@netapp.com]
Gesendet: Donnerstag, 6. April 2017 19:12
An: Alexander Griesser <AGriesser@anexia-it.com>;
toasters@teaparty.net
Betreff: RE: Windows NFS Client + cDOT
Windows NFS clients work with cDOT as of 8.2.3 and 8.3.1. TR-4067 covers this on page 116.
http://www.netapp.com/us/media/tr-4067.pdf
From:
toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net]
On Behalf Of Alexander Griesser
Sent: Thursday, April 6, 2017 1:07 PM
To: toasters@teaparty.net
Subject: Windows NFS Client + cDOT
Hey there,
is it still true that Windows‘ integrated NFS client is unable to mount NFS shares from cDOT systems? Just asking because I was trying to do so again today out of curiosity and failed miserably again.
If this is still the case, can anyone recommend alternative NFS clients for windows?
Best,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601