Linux man pages alphabetic list of all pages. Jump to letter. 3 a b c d e f g h i j k l m n o p q r s t u v w x y z. This section is designed to be the PTES technical guidelines that help define certain procedures to follow during a penetration test. Something to be aware of is that. Simple, caseinsensitive, sitewide, search your browser must allow scripts to run. SSCs Access. NFS Solutions Disk. Share Support FAQDisk. Share Frequently. Asked Support Questions. Rpcinfo No Programs Registered' title='Rpcinfo No Programs Registered' />Q. How do I make a share mountable as Read Only by any NFS client A. By default, a directory is shared as Read Write to every NFS client machine. Change the type of access for the GLOBAL PERMISSION entry in the NFS Permissions dialog for the share to Read Only. Q. How do I deny mount access to all but a selected group of NFS client machines A. Change the GLOBAL PERMISSION entry in the NFS Permissions dialog for the share to No Access. Then push the Add button to bring up the Add Clients and Client Groups dialog. If the names of the machines are not already listed in the upper list box, type their names separated by semi colons in the Add Names entry box at the bottom of th dialog box and press the OK button. For information on client groups, see the Disk. Share Server Utilities section. Q. While adding client nodes in the Add Clients and Client Groups dialog, I get a dialog message box saying The Name XXXX could not be resolved. A. The client name could not be resolved into an address using DNS or the hosts file. If DNS is used, the hostname must be added to the database on the DNS server, otherwise the hostname and address should be present in the hosts file. The Add Names entry field will accept dot notation IP addresses with no host name, but adding the name to the hosts file is the preferred solution. Go To Top. Q. Why do I get the dialog message saying A parent directory of the path has already been shared while trying to share a directory A. NFS rules do not allow a directory to be accessible through more than one share. A parent directory of an existing share may not be exported, nor may a subdirectory of an existing share be exported. Q. Why do I get the dialog message The Global Permission is greater than or equal to an Individual PermissionA. The permission indicated by the GLOBAL PERMISSION entry is what is available to any client machine that mounts the share. It makes no sense to give every machine Read Write access and then indicate one machine has Read Only access. Q. Why does showmount e servername from a client machine return that a shares access is to everyone when I configured the share as Read Only for the Global Permission A. The command showmount e lists which clients that can Mount the share. Clients that have Read Only access are assumed to be able to mount the share. Rpcinfo No Programs Registered' title='Rpcinfo No Programs Registered' />Go To Top. Q. Why do clients still show up as mounted after they have supposedly unmounted from the share A. The client command showmount a servername returns which clients have which shares mounted, which is stored in the rmtab file in the product directory. AppPaths.jpg' alt='Rpcinfo No Programs Registered' title='Rpcinfo No Programs Registered' />If a client does not unmount or unmounts when it cannot access the server across the network, a stale entry can be left in the rmtab file. Also, some NFS clients will not send a correct unmount request if the combined length of the original mount path and server name are greater than 3. In this case, it is suggested that shorter share paths be used if possible. If necessary, the rmtab file may be edited to remove stale entries, but this should be done only while the nfsmount driver is shut down. The recording of client mounts is strictly for informational use and does not affect whether a client actually has access to a share. NFS is a stateless protocol and does not depend on the knowledge of client mounts. Q. I do not want to go through an extra level of menus in File Manager to access existing Lan Manager shares, perhaps to avoid modifying desktop macros. Is there an alternative A. An alternate File Manager Disk. Share user interface is enabled if a value is found in the registry at HKEYLOCALMACHINESoftwareIntergraphDisk. Share DefaultsAlternate. Introducing Windows Server 2003 Pdf. FMUI. File Managers default Share As and Stop Sharing menu items and toolbar buttons are not modified. Instead, control of NFS Shares is done through a separate top level menu with the name Disk. Share, and separate toolbar buttons. Go To Top. Q. What is the Print Spool Destination in the NFS Administrator main window A. A PC NFS client accesses printing services on an NFS server via PCNFSD. When PCNFSD receives a print request from a client, it creates a directory which that client automatically mounts and into which it spools files to be printed. The Print Spool Destination is the parent directory in which PCNFSD creates subdirectories for clients. Q. What is the Print Spool Destination in the NFS Administrator main window A. A PC NFS client accesses printing services on an NFS server via PCNFSD. When PCNFSD receives a print request from a client, it creates a directory which that client automatically mounts and into which it spools files to be printed. The Print Spool Destination is the parent directory in which PCNFSD creates subdirectories for clients. Q. What is the purpose of the NFS Threads section in the NFS Administrator main window A. When Disk. Share is started, a number of worker threads are created to service incoming requests. The NFS Threads sections specifies this number. Q. Why would I want to increase the number of concurrently executing threads A. If an NFS request comes in and all threads are busy, the request does not get serviced until a thread becomes free. Increasing the maximum number of threads may increase response time on a heavily accessed server. Conversly, if other system processing is too slow, the number of threads can be reduced. Go To Top. Q. What is User MappingA. A User Mapping is a concept used to give clients an identity on the Disk. Share server. Most NFS requests contain a UNIX style User Identification Number, or UID. Jumping Beans For Windows 8 more. In the UNIX world, this UID tells the operating system who the requestor is, and what privileges or rights heshe should be afforded. The same idea carries over to the Disk. Share server. Every requesting UID can be mapped to a local user on the Windows NT server. This allows the NFS request to be executed as if it were done by that user locally. User Mappings are also used in reporting User and Group IDs and file permissions. The UID or GID designated as the Default mapping will be the UID or GID reported as the file owner or group. The owner permissions are those allowed for the user who owns the file locally on the server. If the local file is owned by a group to which an ID is mapped, that default GID will be returned as the file group, along with the permissions granted to that group. If there is no group, or the group is not mapped, Disk. Share will traverse the list of GIDs in the NFS request packet and return the first mapped GID which has an entry in the file access list. If no mapped GID is found, GID 6. Go To Top. Q. What about UIDs that are not mapped A. NFS request whose UID is not mapped to a local user or those requests for which no UID is given is mapped to the well known ANONYMOUS LOGON account. This account commonly has limited access on the system. It is recommended that all users who will be accessing the server use a correctly mapped UID. When reporting file permissions for a file owner which has no UID mapped to it, the nouser ID will be returned 6. Q. How does user mapping affect file access permissionsA. When an NFS request comes in from a client, it has a UNIX UID associated with it. Because NT does not understand UIDs, Disk. Share must translate the UID to a local NT user account.