Troubleshoot QNETWARE file system problems

This topic describes various problems that you might encounter when you work with the QNetWare file system and solutions to those problems.

Server does not show up under /QNetWare:

1. Make sure that the NetWare Enhanced Integration NLM is loaded on the server.
2. Use the PING command to check the connection to the server.
3. For better performance, the list of servers is only updated periodically. To force the entire list of servers to be updated, enter CALL QFPNTWE/QFPZCTL PARM(*UPDSRVL).
4. If you are using TCP/IP, make sure that you defined network server attributes.

Users cannot see below the server volumes:

Make sure that the user either has a connection started to the NetWare server or has an authentication entry for the NetWare server or NDS tree.

• To see if the user has a connection started, do this:
  1. On the iSeries™ command line, type WRKNTWCNN and press Enter.
  2. Specify the name of the NetWare server.
  3. Specify the name of the user, and press Enter.
• To see if the user has an authentication entry, do this:
  1. On the iSeries command line, type WRKNTWAUTE and press Enter.
  2. Type 5 on the line by the server or NDS tree to display authentication entries.
  3. If you need to add an authentication entry, do this:
     1. Specify both a server or NDS tree name and the server type in the blank fields.
     2. Type 1 to add an authentication entry for that server or NDS tree; press Enter.
     3. Fill in the remaining fields to create an authentication entry for that user.

Users cannot be authorized to a file or directory:

If you get a message that says Information passed to this operation was not valid when you try to access a NetWare file or directory, ensure that the user exists in the NDS tree and that the NDS context is correct. Either the user's context must be set to the context the user exists in or to the job context, or the system context must be set to the correct context. (Use the NetWare NWADMIN command.)

Users cannot make a directory with MKDIR command:

One of these messages appears:

• Function not supported by file system.

  QNetWare does not support auditing, so you need to specify CRTOBJAUD(*NONE).

• If you get a message that says Information passed to this operation was not valid when you try to make a directory, try one of these solutions:
  • Specify no *PUBLIC authority:

      DTAAUT(*NONE) OBJAUT(*NONE)

    If error CPFA0BC occurs when you use the MKDIR command with DTAAUT(*NONE) OBJAUT(*NONE), use DTAAUT(*INDIR) OBJAUT(*INDIR) instead.

  • Make sure NetWare group EVERYONE was created in your NDS tree and that your job or system NDS context is set to the context that EVERYONE is in.

  Users cannot move a file with the MOV command.

  If you get a message that says Information passed to this operation was not valid when you try to move a file with the MOV command, do this:

  • For NetWare 4.1 and NetWare 5, ensure that the file owner and each user authorized to the file exist in the NDS tree. Also ensure that either their NDS context is correctly set to the context they exist in or to the job context, or that the system context is correctly set.
  • To display the authorized users and owner of a file, you can use the DSPAUT command:
    1. On the iSeries command line, type DSPAUT and press F4.
    2. In the Object field, specify the name of the file; press Enter. iSeries displays authorized users and owners of the file that you specified.

Files that you create by using iSeries Access or an ILE C for iSeries program are always created as read-only.

File modes control how file attributes are set when you create a file. NetWare file mode support shows how NetWare sets these attributes.

Checking the NDS context:

You may want to check the NDS context if you experience problems when authorizing other users to files or directories or moving a file with the MOV command. To display or change the current context, use one of the following commands:

Additional information about NDS contexts:

Requests for network resources or services require identification of the NDS object context in order to locate or create the object. The current context is the position of the NetWare object in the NDS tree. The current context remains in effect until the job ends or until you change it by using the CHGNDSCTX command. The current context changes only for the job in which the command is run.

To identify NDS objects, list the current context and the path from the object to the current position in the NDS tree.