Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Collect the information on the network disk.
    • Network path = "192.168.24.160:/mnt/seaquestdsk0" — Found in "e1039gat1:/etc/fstab"
    • UID = 500 (e1039daq) and GID = 10391 (e1039sc) — Found by "ls -n /data2/e1039_data/slowcontrol_data"
  2. Search for "turn windows features on or off" on the task-bar search box, and click it.
  3. Enable "Services for NFS".
  4. Enable the write permission.
    • Open "regedit" from the task-bar search box.

    • Expand HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> ClientForNFS -> CurrentVersion -> Default.

    • Create a new DWORD value (via right-click menu), with name = "AnonymousUid" and value = "500".

    • Create a new DWORD value (via right-click menu), with name = "AnonymousGid" and value = "10391".

  5. Reboot the OS.
  6. Mount the network disk manually for test.
    • Open "command prompt" from the search box.
    • Execute this command: "mount -o anon -o nolock -o fileaccess=775 \\192.168.24.160\mnt\seaquestdsk0 Z:".  Note that "-o anon,nolock,fileaccess=775" does not work!
  7. Set up an automated mount via startup

Notes:

  • The mount option "-o nolock" was necessary to avoid an error when creating a file: "0x80070021: The process cannot access the file because another process has locked a portion of the file."
  • "UID = GID = 65534" didn't work since the write permission of "/data2/e1039_data/slowcontrol_data" is not granted.
  • It is a bit anxious that any user on the target computer can (re)move any network files by mistake, where such mistake can happen more easily on graphical interface.  A precaution is wanted.
  • The registry can be edited via the command prompt.  Have a try next time:
  • Reference: https://docs.datafabric.hpe.com/61/AdministratorGuide/MountingNFSonWindowsClient.html

...