HOW TO: Configure Performance Settings in Server for NFS

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q324219
This article has been archived. It is offered "as is" and will no longer be updated.
If you are using Server for NFS, you can configure a variety of performance-related settings to tailor Server for NFS to support the site efficiently. This article describes how to configure server settings, authentication settings, and file name handling settings.

back to the top

Description of Performance Settings in Server for NFS

You can use either a command line or Windows Services for UNIX Administration Microsoft Management Console (MMC) to configure server performance settings for Server for NFS. The following list describes the server performance settings that you can configure:
  • Server settings:
    • Enable TCP support: Use this setting to support Transmission Control Protocol (TCP) in addition to User Datagram Protocol (UDP) connections.
    • Enable NFSv3 support: Use this setting to turn on full support for Network File System (NFS) v3 protocol if the client supports it.
    • Directory cache size: The maximum setting that you can use is 128 kilobytes (KB).
  • Authentication settings:
    • Renew authentication: If you use this setting, the default value is set to 600 seconds.
    • Do not renew authentication: If you use this setting, Server for NFS assumes that the client is still authenticated after it has been authenticated the first time.
  • File name handling settings:
    • Translate File Names: Use this setting to specify a character translation file that allows UNIX file name characters to be translated to valid Windows file names.
    • Create files starting with '.' as hidden files: Use this setting to configure Windows to set the hidden attribute on UNIX file names that start with a period (.).
  • Case sensitivity settings:
    • Case Sensitive Lookups: Use this setting to specify that all files are treated as fully case-sensitive.

      When the Case Sensitive Lookups setting is turned off, you can force the case that the file names are returned in by using the underlying file system type, either CDFS, FAT, and NTFS file system. You can either set this functionality to use all lowercase letters, all uppercase letters, or to preserve the existing case.

Setting Performance Settings in Server for NFS

To configure the performance settings for Server for NFS:
  1. Log on to the Server for NFS computer by using an administrative level account.
  2. Click Start, point to Programs, point to Services for UNIX , and then click Services for UNIX Administration.
  3. Click the Server for NFS tab, and then click the Server Settings tab.
  4. Configure the appropriate settings.
  5. Click Apply to apply the changes to the server.
NOTE: For many of the performance settings, you may have to restart Server for NFS if you change the settings. If you turn on the Support for TCP setting, you have to restart the server. To restart Server for NFS:
  1. Right-click Server for NFS, and then click Stop.
  2. Right-click Server for NFS, and then click Start.
back to the top

For additional information about performing maintenance tasks after a migration from UNIX to Windows, click the article number below to view the article in the Microsoft Knowledge Base:
324539 HOW TO: Perform Maintenance and Ancillary Tasks After a UNIX-to-Windows Migration
back to the top


Article ID: 324219 - Last Review: 01/11/2015 04:43:12 - Revision: 2.1

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows XP Professional, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows Services for UNIX 3.0 Standard Edition

  • kbnosurvey kbarchive kbhowto kbhowtomaster KB324219
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)