Known Limitations

The Japanese Unicode code pages for HP-UX and for the Microsoft clients do not exactly match, so there are several ranges of code points (characters) that are supported by Microsoft clients, but not by HP-UX. For example, code points 8740-875D are supported by Windows NT 4.0, but 87XX code points are not supported by HP-UX. AS/U cannot properly handle file or directory names with characters that are not in HP-UX's code pages, even though the clients may support these characters. Be sure to limit the characters in file and directory names to those supported by HP-UX.

The NET command on the HP-UX console accepts Japanese text in the comment, remark, and message fields, except in the case of the NET USER command. If Japanese text is entered into the /COMMENT, /FULLNAME or /USERCOMMENT field of the NET USER command, it will not work properly.

AS/U does not support HP-UX filesystem ACLs.

An ASU user is limited to a maximum of eleven HP-UX group memberships when mapped to a HP-UX user. ASU automatically assigns a mapped HP-UX user to nine ASU pre-defined HP-UX groups. Since HP-UX limits a single- user to 20 groups, only eleven free groups remain.

Event log entries are not overwritten as configured.

Account lockout is not available for WFW clients.

The utility lmshare -q does not display printer queues.

The UIDRULES parameter is ignored.

The del command, when executed from an MS-DOS PROMPT window on a Windows NT 4.0 client, will not work on files on AS/U servers that are not in 8.3 format if the namespacemapping registry entry is not 1 or 3. Use the Windows NT Explorer to delete these files.

The netrun and nvalert services are not supported in AS/U.

RFC NetBIOS on TCP/IP is the only transport protocol supported. The NetBEUI and OSI transports are not available.

AS/U, LM/X, and LM/U can reside on the same system, but CAN NOT be run simultaneously. See the Advanced Server/9000 Installation Guide for procedures on how to toggle between products.

The NT Server / Administrative tools cannot be used to administer Lan Manager for Unix 2.2 (LM/U) or Lan Manager/X (LM/X) servers.

Lan Manager servers should not reside in the same domain as AS/U or Windows NT servers. If a Lan Manager server resides in the same domain as an AS/U or Windows NT server, the NT Domain Security Database will be replicated to the Lan Manager server, corrupting the User Accounts Database on Lan Manager.

If you are migrating multiple Lan Manager servers in the same domain to AS/U, either migrate all servers at once, or move the AS/U servers to a different domain during migration. Clients are able to access servers in multiple domains.

When Advanced Server/9000 is operating in a NIS environment, the registry keyword CreateUnixUser should NOT be used to create UNIX user accounts automatically on the server. When NIS is enabled, the CreateUnixUser keyword should be set to "no". The UNIX user should be created using standard UNIX commands and the AS/U user should be mapped to the UNIX user using mapuname.

The net accounts /role command is not available with AS/U. Use the Server Manager from a PC to change a server's role within a domain.

The join domain utility in /opt/asu/lanman/bin can also be used to change the role of the server..

Filenames created with European characters by ms-dos/win16 clients are not preserved when migrating from LM/U to AS/U. A conversion script (asu_pcuxconv) is provided to convert filenames after migration. (Refer to the section "Converting European filenames from LM/U to AS/U" above.)

Windows 95 and German umlauts You cannot administer resource permissions on shares that contain German umlauts in their names from the Explorer. Permissions can be administered if the resource is accessed through the Network Neighborhood. Microsoft has acknowledged this behavior but has indicated that it is by design and no fixes will be forthcoming.