Novell Native File Access Protocols

CIFS Issues

• CIFS does not currently support certain double-byte characters used in file and directory names. Specifically, the double-byte backslash (\) and the double-byte dash (-) characters do not work. (The Unicode value for the double-byte backslash is 0xFF3C; the Unicode value for the double-byte dash is 0x817C.) We recommend that you use the single-byte backslash and dash characters in file and directory names.
• You must use ConsoleOne^® to manage CIFS passwords for users who have double-byte characters in their username.
• Once you have installed the NetWare^® 6 Support Pack 1 software, you should configure your Windows/CIFS network environment with ConsoleOne. Previously, CIFS parameters were configured by manually editing the CIFS.CFG file. That file now contains a note telling you to use ConsoleOne for CIFS configuration.

  If eDirectory^TM is reinstalled on a server running CIFS with NetWare 6 Support Pack 1, ConsoleOne CIFS management will not automatically reimport the CIFS.CFG configuration into ConsoleOne. To reimport the configuration, remove the comment lines starting with ### from SYS:ETC\CIFS.CFG and then run CIFSSTOP and CIFSSTRT.

• Unicode must be enabled on a CIFS server in order for DFS junctions to work. You can enable Unicode in the following ways:
  • During the Installation: Make sure the Enable Unicode check box is checked on the first Server Properties screen.
  • After the Installation Using ConsoleOne^®: Right-click the Server object in ConsoleOne and then click Properties > CIFS > Config. Make sure the Unicode check box is checked and then restart CIFS by running CIFSSTOP and CIFSSTRT.

• A new CIFS.NLM corrects a problem with the domain import function. For more information, see TID #2960727 on the Novell Support Knowledgebase.
• In Domain mode, when the CIFS server is selected as a master browser, it maintains a list of servers in the domain only on the local subnet. Subsequently, servers in the domain that are located on other subnets will not appear in Network Neighborhood.

Macintosh/AFP Issues

• Copying an executable file that has an extended character (such as diacriticals) in its name to an NSS volume will result in an error (-43 "File not found"). Rename the executable file without extended characters and then copy the file to the NSS volume.
• When you drag nested folders to the Trash from a workstation running Mac* OS X, an error message says that the folder is in use. You should drag files as a group to the Trash and then drag the folder to the Trash.
• When you move or copy a file or folder to the same volume from a workstation running Mac OS X, the action is performed properly but you will see an error (-43 "File not found"). You can safely disregard this error message.
• Version 2.2 of the Apple* Filing Protocol (AFP) limits filenames to 31 characters or less while the Mac OS X implements AFP 3.0, which supports filenames longer than 31 characters. Because the AFPTCP NLM^TM uses AFP 2.2, you should keep your filenames to 31 characters or less to successfully copy and move files to an AFP volume.

UNIX/NFS Issues

• Upon executing makenis in a server with no replica when the Master replica is down, instead of displaying a DS error, a series of messages similar to the following are displayed erroneously:

  Nullpointer passed to routine Kmutex

• Do not use makenis to delete users and groups. Use ConsoleOne^® instead.
• If the pkernel screen displays messages similar to the following on executing yppush, you can ignore them (they do not affect functionality in any way):

  Out of memory, cannot create UDP Client handle.