UNIX / NFS Issues

Upgrade Issues

• Before beginning an upgrade from NetWare 5.0 with NetWare NFS Services 2.4 installed, you must comment out the UNISTART entry in AUTOEXEC.NCF.
• Before rebooting the system after an upgrade from NetWare 5.1 with ZENworks^TM for Desktops 3.2 and PXE support installed, you must change the load order in AUTOEXEC.NCF so that NFSSTART.NCF comes before ZFDSTART.NCF.
• Upgrading from NetWare 5.1 with NetWare NFS* Services 3.0 installed removes the product but retains the NFS Server and NIS configuration.
• After an upgrade from NetWare 5.1 with NetWare NFS Services 3.0 installed, you must remount the NetWare exports mounted on NFS clients.
• After upgrading from NetWare 5.1 with NetWare NFS Services 3.0 installed, the NFS Gateway component of NetWare NFS Services 3.0 will not be functional; it is not supported on NetWare 6.

General

• If the server holding the master eDirectory^TM replica is down, Native File Access for UNIX* will not work on servers that have a Read-Only replica, a Filtered replica, or no replica.
• When Native File Access for UNIX is installed on a multiserver tree, the UNIX profile of the NIS User object is not mapped to root. Therefore, NFS Server fails to load.

  Refer to the SYS:ETC\SCHINST.LOG file after the installation and run schinst again if any errors are logged.

• If the pkernel screen displays messages similar to the following, you can ignore them (they do not affect functionality in any way):

  RPC:svc_register failed for prog=186A4, vers=1

  NOTE:  This issue is resolved in NetWare 6 Support Pack 1.

• When Native File Access for UNIX is installed, the nfsstart entry is added to AUTOEXEC.NCF, so the services are not automatically available after installation.

  To make Native File Access for UNIX available, run nfsstart after installation or reboot the server.

ConsoleOne

• If you administer NFS exports of multiple servers and switch between them, it is possible that the data you view is for the previous server.

  Click the corresponding Server object, right-click Exports, and then click Refresh to display its data.

• When managing the NFS server through ConsoleOne, if you try to export a volume without logging in to the Novell eDirectory tree, the following message displays erroneously: Config file is open.

  To export a volume, log in to the Novell eDirectory tree.

  NOTE:  This issue is resolved in NetWare 6 Support Pack 1.

• When managing NFS Server through ConsoleOne, if a value that is out of range or invalid is entered in NFS Server > Options > Parameters, a cursor is placed in the next field and you cannot modify that field.

  To modify the field, close the panel and open it again. Enter a valid number that is in the range in the NFS Server > Options > Parameters field.

  NOTE:  This issue is resolved in NetWare 6 Support Pack 1.

• When managing NIS through ConsoleOne, eDirectory objects of type ipService and nisObject cannot be created.
• When performing special map migration through ConsoleOne, the complete path of the file is required (for example, SYS:ETC\NIS\PHLIST).

  NOTE:  This issue is resolved in NetWare 6 Support Pack 1.

• Administering NetWare 5 NFS Services on NetWare 5 from ConsoleOne on NetWare 6 is not supported.

NFS Server

• If exported NSS volumes are deactivated and activated in a different order, operations from an NFS client on these mount points will fail.

  To ensure proper functionality, unload and reload the NFS Server software and remount the exported path on the NFS client.

• Hard links are not supported on exported NSS Volumes.
• Traditional volumes can be mounted only using NFS version 2.

  Even though showmount shows the volumes as exported, they are not mountable using NFS version 3. You need to explicitly mount the exported traditional volumes specifying the mount version as 2.

• If a Windows workstation user who has write permission to a file created in a mounted volume by a UNIX user attempts to modify the file, the ownership of the file will change from the UNIX user to the Windows workstation user.
• UnixWare* 7 NFS client access has issues with recursive delete and C file compilation. Also, the ownership of a file will change if a nonowner user with permissions to the file edits it.

NIS Server

• No error message is displayed to convey that the NetWare server fails to become a slave to the UnixWare 7 NIS Master.
• To set the password for a user from a UNIX NIS client, use ypset to set the default domain in the NetWare server.
• NIS objects such as nisDomain, nisMap, and nisObject cannot have names with more than 64 characters.
• Unloading nisbind might take several minutes.
• If maps are pushed to an NetWare NIS slave server using any map name (for example, hosts.byname or hosts.byaddr), both maps are updated in the slave server.
• For Default maps, the pound sign (#) is not a valid comment character. If you don't want to migrate a particular record, remove it from the text file before migrating.
• The bootparam and netgroup maps are not supported in this release.
• Using ypcat groups does not show the members of the group.

  NOTE:  This issue is resolved in NetWare 6 Support Pack 1.

Migration

• After a new user is created and the user's UNIX profile is set, if the group corresponding to the user's GID exists, the user will be listed as a member of that group. However, the rights of the group will not flow down to this user. Remove the user from the members list and add it again.
• While migrating domains using the -x option, edit the context parameter by prefixing each of the dots in the Relative Distinguished Names with a backslash ( \ ) to distinguish them from eDirectory (NDS) names.