Windows Server
United States (English) Sign in
Home Windows Server 2012 Windows Server 2008 R2 Windows Server 2003 Library Forums
TechNet Library
Windows Server
Windows Server 2008 R2 and Windows Server 2008
Troubleshoot Windows Server
Troubleshoot Windows Server 2008 R2
Best Practices Analyzer
Best Practices Analyzer for File Services
Best Practices Analyzer for File Services: Configuration
DFS-N: The DFS Namespace service startup type should be set to Automatic
DFS-N: All IP addresses for the server should map to the same AD DS site
DFS-N: The LDAP timeout value should be set to the default value of 30 seconds
DFS-N: The DFS Namespaces sync interval should be set to the default value of 1 hour
DFS-N: Site costed referrals should be enabled on domain controllers
DFS-N: Client failback should be enabled for the Netlogon and SYSVOL folders on domain controllers
DFS-N: Namespace root referrals should use the Lowest Cost ordering method on the following DFS namespace
DFS-N: Failover Clustering should be enabled on the server hosting the following standalone namespace
DFS-N: Additional namespace servers should be added to the following domain-based namespace
DFS-N: Windows Server 2008 mode can be used on the following domain-based namespace
DFS-N: The access-based enumeration setting should be identical in the DFS namespace database and on the shared folder hosting the namespace root for the following namespace
DFS-N: Client failback should be enabled on the following namespace
DFS-N: The namespace server should be enabled on the following namespace
DFS-R: The DFS Replication service should be started and have a startup type set to Automatic
DFS-R: Replicated folder must be enabled for replication
DFS-R: Servers '{0}' and '{1}' belonging to the replication group '{2}' must have two-way connections between them
FSRM: File Server Resource Manager should be installed on all nodes of a failover cluster
FSRM: The shadow copy storage area should be large enough for File Server Resource Manager to create snapshots of files
FSRM: Classified files should have read/write attributes
FSRM: File paths should be shorter than 240 characters
FSRM: Alternate data streams should be large enough to store classification properties
FSRM: The cache for classification properties should be active
FSRM: There should be fewer than 1000 file screens configured on the server
FSRM: There should be fewer than 1000 quotas configured on the server
FSRM: There should be fewer than 20 classification properties
FSRM: Classification rules should have schedules
FSRM: Notifications that use variables that reference remote paths should reference valid shared folders
NFS: The domain functional level should be Windows Server 2003 R2 or higher when using an identity mapping solution
NFS: Folders that are shared by using both the SMB and NFS protocols should use mapped accounts
NFS: Server for NFS should be configured to use Netgroups
NFS: Services for Network File System should use an RFC 2307-based identity mapping solution
NFS: Operating system case sensitivity should be disabled for file servers that support the NFS and SMB protocols
NFS: Windows Firewall should open all ports used by Services for Network File System
NFS: Services for Network File System should be used or uninstalled
NFS: The Server for NFS service should be started
SMB: The Server service should be set to start automatically
SMB: The Workstation service should be set to start automatically
SMB: File and printer sharing ports should be open
SMB: Previous Versions support for client computers running Windows 98 should be disabled
SMB: The SMB 2.0 file sharing protocol should be enabled
Expand Minimize
This topic has not yet been rated - Rate this topic

NFS: The Server for NFS service should be started

Published: July 10, 2010

Updated: February 2, 2011

Applies To: Windows Server 2008 R2

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the File Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

 

Operating System

Windows Server 2008 R2

Product/Feature

File Services

Severity

Error

Category

Configuration
The Server for NFS service is not running on this server.
Client computers will not be able to access NFS shares on this server.
Start the Server for NFS service.

Membership in the Administrators group, or equivalent, is the minimum required to complete this procedure.

  1. Click Start, right-click Command Prompt, and then click Run as administrator.

  2. To start Services for NFS, type: sc start nfsadmin.

  3. To confirm that the service is in the Running state (also known as the Started state), type: sc query nfsadmin.

Did you find this helpful?
(1500 characters remaining)

Community Additions

ADD
© 2013 Microsoft. All rights reserved.