Dell PowerVault 715N (Rackmount NAS Appliance) - Manual (Page 104)

Every time I
try to obtain a
directory
listing from an
NFS client on
the root of a
system
volume, I get
an error
message, such
as Permission
Denied
.
The problem you are experiencing involves a System Volume Information
directory created by Microsoft Index Server. The NFS service does not have
access to this directory and returns an error message to the client when trying to
list its properties.
This issue only occurs when sharing the root of a drive letter.
Ignore this error.
The System
Volume
Information
directory is not
used by NFS clients
or your system by
default.
Sometimes I
am unable to
delete folders
that have been
used and that
are shared to
an NFS client.
This is a situation that occurs with NFS discretionary access lists (DACLs) and
inheritance. When the folder to be shared is created, the only access control
entry (ACE) created by default is Everyone with Full Control. When an NFS
client creates a directory or a file in this directory (mounted share), Services for
UNIX (SFU) creates a new DACL that replaces the inherited Everyone with Full
Control ACE. This DACL contains an Everyone ACE with the appropriate UNIX
file creation access and may contain two other ACEs for the mapped user and
group. If this happens, the administrator of the Windows client cannot delete the
file or directory unless that administrator takes ownership through the Windows
system and changes the access.
As the
administrator, use a
Windows client
system to take
ownership and
change the access
to allow yourself to
delete the share
folders.
When you delete
the NFS share
folders, ensure that
there are no open
file handles for the
share. If you are
unsure, delete the
share, and then
restart NFS.
When updating
client access
to an NFS
share, the All
Machines
client group is
reset from the
No Access
access type to
Read-Write
access.
The NAS Manager might reset the All Machines client group to Read-Write
when there are no clients that have read-only or read-write access.
Add a client that
has read-write or
read-only access,
and then set the
All Machines client
group to No
Access.
Table 8-7. Macintosh and AppleTalk
Issue Possible cause Resolution
I am getting event errors for Services
for Macintosh.
Services for Macintosh are bound to the onboard
network interface controller (NIC) by default. If this
NIC has been disabled, binding errors occur.
Bind the AppleTalk protocol
to an enabled NIC. See
"AppleTalk Protocol
Adapter Binding" in
"Advanced Features."
From a Macintosh client, users cannot
modify or delete a file that a Windows
client has accessed.
The time between clients and the system is not
properly synchronized.
Make sure that clients
have their time
synchronized to within
10 minutes of the time
zone.
I have rebooted my NAS system from
a Macintosh client. Several minutes
have passed and my NAS system has
not rebooted or the page has not
refreshed.
The most likely cause is that the NAS system has
come back online, but the client screen has not
refreshed because the PowerVault NAS Manager
does not automatically refresh the screen when the
NAS system has finished rebooting.
Close Internet Explorer,
and then reconnect to the
NAS Manager. The NAS
system should behave
normally.
From a Macintosh client, I cannot
connect to the administration part of
the PowerVault NAS Manager by using
the Administer This Appliance link
on the HTTP Shares page.
The internally generated certificate is not supported
by Internet Explorer for Macintosh.
You can administer the
NAS system by using the
address
http://servername :1278
;
however, this is a
nonsecure link.
After modifying properties of the File Services for Macintosh can not establish Restart the workstation