Connecting to the primary computer using NFS

To use NFS file sharing, you must configure NFS on the primary computer so the /aiw filesystem is accessible to the Windows application server. The share is then mounted on the Windows application server.
To connect to the primary computer using NFS:
  1. On the application server, verify File Services are installed for the Network File System:
    1. Press Windows Key+r to open the Run dialog box and type:
      appwiz.cpl. This opens the Programs and Features window.
    2. In the Program and Features window, click Turn Windows Features on or off.
    3. Follow the instructions in the features wizard to make sure that NFS is installed.
      • For Windows Server 2019, install NFS by selecting Features → Client for NFS.
      • For Windows 10 Pro or Enterprise, install NFS by selecting Services for NFS → Client for NFS.
          Note:
        • Client for NFS is only available on Windows 10 version 1703 or later.
  2. Add registry entries to configure NFS with the UID and GID used to access files:
    1. Log in to the primary computer.
    2. In a command prompt type id <system_user> where <system_user> is your system user ID (default aiw1).
    3. Note the UID and GID numbers and convert them to hexadecimal format.
      Note: The UID is the system user ID (default aiw1) and the GID is the system group ID (default aiwgrp1). They are specified in hexadecimal values in the registry, for example, the default UID of 32457 is 0x00007ec9, and the default GID of 32458 is 0x00007eca.
    4. On the application server, create a file named nfs.reg.
      Note:

      You can create nfs.reg, anywhere on your system.

      Make sure you have file extensions showing. If you do not display file extensions, the file is created as a text file, not a registry file.
    5. Edit nfs.reg so it contains the following contents:

      Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default]
"AnonymousGID"=dword:<GID_hex>
"AnonymousUID"=dword:<UID_hex>

    6. Replace <GID_hex> with the GID hexadecimal number starting after the 0x. For example, if the GID hexadecimal number is 0x00007eca, replace <GID_hex> with 00007eca.
    7. Replace <UID_hex> with the UID hexadecimal number starting after the 0x. For example, if the UID hexadecimal number is 0x00007ec9, replace <UID_hex> with 00007ec9.
    8. Save nfs.reg and close the file.
    9. Double-click nfs.reg to run the registry file, which adds the UID and GID values to the registry.
      Note: Make sure that the values in the registry file exactly match the instructions. Incorrect registry modification can damage your operating system.
    10. Delete nfs.reg from your system.
    11. Restart the NFS service by typing the following commands into a command prompt:
      nfsadmin client stop
      nfsadmin client start
      If you receive error messages when stopping or starting the NFS service, restart the application server computer.
  3. On the application server, map the /aiw filesystem from the primary computer using the Map Network Drive dialog in Windows and this address for the server:
    \\<primary_server_hostname>\aiw
      Note:
    • If the connection fails, map the filesystem manually. Open a Command Prompt, and type: mount primary_server_hostname:/aiw drive_letter.
  4. Test the configuration by creating a file in the <drive_letter>:\aiw1 directory and then deleting it.
  5. Note the name of the drive for use during the installation process.
  6. Continue with Installing application servers on Windows computers.

Related information:

Application server does not connect
Parent topic: Preparing a Windows application server