NetWare Directory Services

2-25
Understanding NetWare Directory Services
Context and Names
For more information on NetWare Server objects, see “Object” in Concepts.
Naming Restrictions for Bindery Services
When you create objects to be accessed from workstations running the
NetWare Client shell (NETX), the names of the objects must follow bindery
naming rules or these clients cannot recognize them. Object names in
bindery services are interpreted as follows:
• Spaces in object names are replaced by underscores
• Object names are cut off after the 47th character
You cannot use the following characters in an object name that must be
accessed from a workstation running the NETX client:
/ slash
\ backslash
: colon
, comma
* asterisk
? question mark
NOTE: The object naming rules apply to most objects. Additional rules applying to NetWare
Server objects and objects viewed through bindery services are described in a
separate chapter. See chapter 4 for more information.
Naming Restrictions for International Support
Unicode is a wide character encoding scheme that provides the basis for
internationalization of the information in an NDS database. All character
strings exchanged between an NDS server and a client workstation are in
Unicode. The NetWare Client software handles the translation of Unicode
strings.
Occasionally, however, you might use characters that Unicode cannot
translate. When this happens, the character is substituted in your display as a
“heart” symbol in DOS and as a box (q) in Windows.
Substituted characters can prevent NDS from recognizing an object. See
“Unicode” in Concepts for more information.