C.1 General FAQs

This section has general FAQs for Native File Access for UNIX.

C.1.1 When upgrading to NetWare 6.5 from NetWare 5.1 / NetWare 6.0, I am receiving a file overwrite warning for nfsstart.ncf. What should I do?

Select to overwrite the existing nfsstart.ncf file.

C.1.2 NFS Server is not loading on a server in tree with NetWare 5.1 NDS 7 replica ring. How can I resolve this?

For complete and correct functionality, ensure that the entire replica ring for any partition containing the NFS search_root contexts are on eDirectory 8.0 or later.

C.1.3 When I try to load NFS Services using Ndsilib.nlm, -669 error displays on the logger screen. How can I resolve this?

Manually execute schinst -n -w on system console.

Or

If the error continues even after executing schinst, then do the following:

  1. Make a note of all the nodes that share the NFAUUser object in that context.

  2. Delete the NFAUUser object.

  3. Run schinst -n -w on all the nodes that you made note of in Step 1.

C.1.4 When the administrator changes the UNIX profile of the user, the updated profiles are not cached immediately. How can the profile be updated immediately?

The profile gets updated after two hours. To update the profile before this time in the system console, execute ndsilib cache refresh.

C.1.5 What is the significance of the SEARCH_ROOT parameter in SYS:ETC\NFS.CFG file?

This parameter is a list of contexts under which NFS* modules search for users that have their UNIX* profile populated.

There are some rules that need to be observed to add to this search list:

  • The specified contexts should begin with a period (.)

  • Contexts can be specified as .Ou1.Top or as .Ou=Ou1.O=Top

  • Items in the list must be separated by commas (,) but no spaces.

C.1.6 How do I manually set the UNIX profile of a user?

After the product installation is complete and the schema has been extended to have UNIX attributes, appropriate ConsoleOne® snap-ins are now available to populate those attributes.

To populate the UNIX attributes, follow these steps:

  1. In ConsoleOne, select an existing Group object or create a new Group object.

  2. Right-click this Group object and then click Properties.

  3. Go to the UNIX Profile tab and specify the desired GID Value.

  4. Select/create a User object whose UNIX profile needs to be updated.

  5. Right-click this User object and then click Properties.

  6. Click the UNIX Profile tab and then specify the desired UID Value.

    For the Primary Group field, specify the GID specified in Step 3 and then click on Apply/OK.

Now there is a user whose UNIX profile is populated; but to make this visible to NFS modules, this User’s context or one of its parents' context needs to appear in the SEARCH_ROOT parameter in SYS:ETC\NFS.CFG. For this change to get reflected (if a fresh context was added to the SEARCH_ROOT list), do an nfsstop and nfsstart again.

C.1.7 How do I set a User’s UNIX profile to the Root’s profile?

In Step 6 above, setting the UID Value to 0 in the User ID field attaches the root profile to that User object. Again, make sure that either this User’s context or one of its parents' context is in the SEARCH_ROOT list.

C.1.8 Could not authenticate ContextHandle. Load schinst and try again. Exiting...9601

In the following procedure .NSC = Organization name in the eDirectory tree.

  1. Ensure that in the NFS.CFG, the NIS_ADMIN_OBJECT_CONTEXT is set to .NSC or .O=NSC and that SEARCH_ROOT also has the same context in the same format and is preceded by a dot (.).

  2. Execute nfsstop and run SCHINST.NLM (get the SCHINST.LOG and NFS.CFG after this).

If this does not work, then do the following:

  1. Make a note of all the nodes that share the NFAUUser object in that context.

  2. Delete the NFAUUser object.

  3. Run schinst -n -w on all the nodes that you made note of in Step 1.

  4. Capture the log and configuration files and see if it works.

C.1.9 When I execute nfsstart after reinstalling the directory services in the server or joining the server to an existing tree or deleting the NFAUUser object, messages such as "Error unloading, killed loaded module (ndsilib.nlm)", or "Unable to Login.: error -669 Could not authenticate ContextHandle. Load schinst and try again. Exiting...-669" display. What should I do?

You need to do the following:

  1. Execute nfsstop.

  2. Execute schinst -n -w

    1. (Conditional) When you reinstall the directory services in the server or join the server to an existing tree, run nisinst.

  3. Execute nfsstart.

C.1.10 While executing the SCHINST -n, what does the message “Error: Unable to login. Error Code: 35076” imply? This is displaying even when the Schema is fine and nfauuser object has been recreated.

This implies that the server’s /etc/hosts file does not contain the simple host name (server name).

To resolve this, do the following:

  1. Make sure that the server's /etc/hosts file contains the simple host name (server name).

    For example, if the format is

    192.168.2.3 server1.domain.com

    then change the entry to,

    192.168.2.3 server1.domain.com server1

  2. Restart the server and schinst should work fine.

C.1.11 During nfsstop, ndsilib.nlm does not get unloaded and it displays a message showing dependency on nwftpd.

NetWare FTP Server (Nwftpd.nlm) has a dependency on ndsilib.nlm. So if nwftpd.nlm is running, unloading ndsilib.nlm through nfsstop.ncf will fail. To avoid this, please unload nwftpd.nlm first and then unload ndsilib.nlm