|
Symptoms
- StorageExpress™ system and DOS Shell (NETX) clients cannot see and/or cannot log into a NetWare* 4.x server. Any attempts at logging into a NetWare 4.x server from a DOS Shell (NETX) client such as the StorageExpress system results in an ACCESS DENIED message at the client. The server will ask for a password even if the specified username has none. When the command 'CONFIG' is used at the console prompt, bindery context shows properly.
- A new NetWare 4.11 server has just been added to an existing NetWare 3.x network. The StorageExpress system and DOS Shell (NETX) clients can neither see the server via SLIST nor log into it via user Admin. When the command 'CONFIG' is used at the console prompt, nothing shows as set. However, when the 'SET BINDERY CONTEXT = OU=<ou_name>.O=<o_name>' command is used at the console prompt, a 'BINDERY CONTEXT ALREADY SET' message is returned.
Description
Either the NDS was not installed correctly, or it has become corrupted.
Solution
WARNING: The possible solutions listed below should only be attempted by personnel experienced and/or trained with the workings of the NDS and NetWare!
- Try to reset bindery context and cycle the NetWare 4.x server. Also try running DSREPAIR.
Attempting to reset bindery context and cycling the NetWare 4.x server may not prove effective. Also, DSREPAIR may return a message stating that it has aborted due to the local database not being open.
- On larger NDS Trees which contain many objects, try the following:
Download DS410A.EXE from http://support.novell.com
† and use the DSREPAIR contained within to unlock and repair the database. This should allow the StorageExpress system and DOS Shell (NETX) clients to see and log in to the 4.x server.
WARNING: Novell warns that this version of DSREPAIR is acceptable to use on a 4.11 server, but DO NOT use any other files in DS410A.EXE patch kit on a 4.11 server!
- On a new server with little or no extra objects other than the default, try the following:
Using the DSREPAIR matched to your version of NetWare 4.x, type 'LOAD DSREPAIR -DSREMOVE' at the system console. This will force Directory Services to close. While in the INSTALL program, try reinstalling Bindery Context. This should allow the bindery context to reset and allow the StorageExpress system as well as DOS Shell (NETX) clients to see and log into the NetWare 4.x server.
† This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.
This applies to:
| 
