Remote mount failed

If mount fails for any reason, check the sections below for specific details about what to do. They are arranged according to where they occur in the mounting sequence and are labeled with the error message likely to be displayed.

mount: can't open /etc/mnttab

The table of mounted filesystems is kept in the file /etc/mnttab. This file must exist before mount can succeed. The file /etc/mnttab is created when the system is booted and it is maintained automatically after that by the mount and umount commands.

mount: / is already mounted, name is busy, or allowable number of mount points exceeded: Device busy (error 16)

The requested filesystem is already mounted.

mount: name or name, no such file or directory

The -f option or server name was probably omitted from the command line. The mount command assumes that a local mount is being done unless the -f flag is used on the command line or the requested directory as listed in /etc/default/filesys specifies filesystem type NFS.

This message also appears when the specified local mount point is not an existing directory.

mount: can't open /etc/default/filesys

The mount command tried to look up the information needed to complete a mount request in /etc/default/filesys, but there was no such file. As the system administrator, you need to create this file as part of initial system setup.

mount: sys_name not in hosts database

The system name specified on the mount command suffixed by the ``:'' is not listed in the file /etc/hosts or with the Domain Name Service (DNS). Check the spelling of the host name and the placement of the colon in the mount command.

mount: directory argument name must be a full pathname

The second argument to mount is the path of the directory to be covered. This must be an absolute path starting at slash (/).

mount: ... server not responding(1):

RPC_PMAP_FAILURE - RPC_TIMED_OUT

Either the server to which the mount is being attempted is down or its portmapper is dead or hung. Attempt to log in to that machine; if you succeed, then the problem may be in the portmapper. Run the following command from your system as root to test the portmapper on the server system:

rpcinfo -p host_name

If the resulting display does not show the portmapper, stop and restart NFS on the server with these commands:

nfs stop
nfs start

If the server is up but it is not possible to reach it using ping, check the client's network connection by trying to ping another machine. Also, check the server's network connection.

mount: ... server not responding:

RPC_PROG_NOT_REGISTERED

mount got through to the portmapper, but the NFS mount daemon mountd was not registered. Check the server to ensure that /etc/mountd exists and is running.

mount: /dev/nfsd or directory_name, no such file or directory

Either the remote directory does not exist on the server or the local directory does not exist. Again, note that /dev/nfsd is always printed to represent the remote directory.

mount: access denied for sys_name:name

The client machine on which the mount attempt is being made is not in the server's export list for the filesystem to be mounted. A list of the server's exported filesystems can be obtained by running:

showmount -e host_name

If the desired filesystem is not in the list or the machine name is not in the user list for the filesystem, then check the /etc/exports file on the server for the correct filesystem entry. A filesystem name that appears in the /etc/exports file but not in the output from showmount indicates a failure in mountd. Perhaps it could not read that line in the file, or it could not find the filesystem, or else the filesystem name was not a locally mounted filesystem. See exportfs(NADM) and exports(NF) for more information.

This message can also be an indication that authentication failed on the server. It may be displayed because the machine that is attempting the mount is not in the server's export list; check the server's /etc/exports file.

mount: name: no such file or directory

The remote path on the server is not a directory.

mount: not super user

The mount command can be used only by root, because it affects the filesystem for the entire machine.

Choose an Enforcement Method

Updated: October 6, 2008

Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

To choose the right NAP enforcement method for your network, review the following sections of this guide to understand the details of how each enforcement method works and determine which method best meets your deployment goals:

You might also consider the following when choosing an enforcement method:

Infrastructure. How well does your current network support the enforcement method?
Cost. Which aspect of your NAP deployment is more important: cost or flexibility?
Complexity. Do you have the expertise to implement and maintain your deployment?
Security. How secure is the enforcement method?

Infrastructure

All NAP enforcement methods can be implemented using a minimum of one computer running Windows Server 2008 R2 or Windows Server 2008. All enforcement methods require that NPS is installed on this computer and configured to evaluate the health of NAP clients. Additional required services depend on the enforcement method. For example, IPsec, VPN, and DHCP enforcement methods require a NAP enforcement server running Windows Server 2008 R2 or Windows Server 2008. The 802.1X enforcement method requires network hardware that supports the 802.1X authentication method and is capable of controlling port characteristics using RADIUS tunnel attributes. For more information, see NAP Configuration Overview.

MCITP Boot camp USA : MCITP CCNA Boot camp UK, MCITP MCSE CCNA Boot camp Asia, MCITP CCNA MCSE Bootcamp, MCITP MCSE RHCE Training

Cost

Because support for it is built into the Windows operating system, the cost of deploying NAP is typically low, but depends on how well your existing network hardware and software support your design. If you have deployed Windows Server 2008 R2 or Windows Server 2008 on your network, then you already have some or all of the components required to deploy NAP. Some NAP enforcement methods might require an upgrade of the components of your network infrastructure. For example, deploying NAP with 802.1X enforcement can be costly if you do not already have hardware that supports 802.1X authentication. If you already have hardware that supports 802.1X, then it is likely that you can deploy NAP with 802.1X enforcement at minimal cost. If your hardware does not support NAP, in some cases adding support can be as simple as downloading and installing new firmware. To determine the costs associated with a NAP deployment, review hardware and software requirements for the enforcement methods you have chosen and determine whether server and network hardware upgrades are required. Additional costs that might also be associated with a NAP deployment include planning and design costs and the training of support personnel.

Complexity

NAP with IPsec enforcement is generally the most complex enforcement method to deploy because it requires a public key infrastructure (PKI) and IPsec policies to create logical networks. However, Windows Server 2008 R2 and Windows Server 2008 include tools for managing and monitoring IPsec that eliminates much of this complexity. The 802.1X enforcement method is next in terms of complexity, followed by VPN enforcement. DHCP enforcement is the least complex enforcement method to deploy.

Security

IPsec enforcement is a powerful method for protecting compliant computers from any others; it can be combined with server and domain isolation to ensure that after a computer has demonstrated it is compliant, it will still be restricted to communicating only with authorized hosts. IPsec provides other benefits, too. Network packets are authenticated, which reduces the risk of man-in-the-middle and replay attacks, and traffic can be encrypted with IPsec, providing a high degree of protection from eavesdropping attacks.

Like IPsec, 802.1X offers a high degree of protection. Several enhancements to 802.1X are also available that provide improved security. Until a client has demonstrated that it complies with the organization�s health requirements, its access to the network will be restricted by the network switches and wireless access points. These restrictions can be very difficult to bypass, even by a determined malicious user.

VPN enforcement is a good choice for protecting remote access to the corporate network. Clients that connect to a NAP-enabled VPN server can be granted restricted access to the network at the point of entry using IP packet filters. The health of remote client computers is evaluated when the client connects and it is monitored during the VPN session. If a client computer becomes noncompliant, then access is restricted until the computer is compliant.

DHCP enforcement restricts noncompliant computers by providing a limited IPv4 address configuration. It is the least secure NAP enforcement method. It is easily bypassed by an advanced user who has administrative privileges on the computer.

Combining NAP enforcement methods

It is possible to use more than one enforcement method simultaneously. An organization might invest additional resources into combining these enforcement technologies because they have complementary strengths and weaknesses. NAP with VPN enforcement can be used to enforce organizational compliance policies on remote clients, while NAP with IPsec enforcement can be used for local clients. 802.1X and IPsec offer a particularly robust combination because together they can restrict network connectivity at multiple layers of the network protocol stack. The following table shows which enforcement methods can be combined. Keep in mind that the complexity of your NAP deployment will increase when you combine enforcement methods.

	IPsec	802.1X	VPN	DHCP
IPsec
802.1X			X
VPN		X		X
DHCP

Microsoft Course 20413