Novell Home

My Favorites


Please to see your favorites.

Permanent Bad Name Cache

This document (7015227) is provided subject to the disclaimer at the end of this document.


Novell Client 2 SP3 for Windows (IR8)


Poor performance when attempting to contact network resources.
How to identify resources that the Novell Client should never attempt to resolve as NCP servers so that Windows will more quickly attempt to resolve them through other network clients (e.g. the Microsoft Client).


The Novell Client includes a "Bad Address Cache." If the Client is unable to establish a TCP-level connection to a particular IP address, it stores that address in the Bad Address Cache.
The Advanced Setting "Bad Address Cache Timeout" specifies the number of seconds a Bad Address will remain in the Bad Address Cache.   
Because the Client must first determine that a given resource is not reachable, there is a delay the first time the Client tries to locate a resource, but subsequent attempts will be fast, due to the entry existing in the bad name cache. Elimination of the initial delay is made possible by pre-populating a bad server name cache.
Beginning with Novell Client 2 SP3 for Windows (IR8), a bad server name cache is available. Establishing a bad server name cache can correct performance problems caused by delays in attempting to locate resources which are not findable by the Novell Client. Currently, this functionality is controlled via registry entries (no user interface is currently available).
The Novell Client reads the bad name cache from the registry during the system initialization and blocks any login attempts by the Novell Client to any server name listed.
The registry values, located under the subkey [HKEY_LOCAL_MACHINE\Software\Novell\Client\Parameters] are:

BadNameCacheEnabled of type REG_DWORD.
BadNameCacheList of type REG_MULTI_SZ.

"BadNameCacheEnabled" can have a value of 0 (disabled) or 1 (enabled).  Explicitly enabling the Bad Name Cache is optional, since effectively, the Bad Name Cache is enabled any time the "BadNameCacheList" contains one or more server names or wildcard patterns. This means that the feature will be enabled if "BadNameCacheList" exists even if the "BadNameCacheEnabled" does not exist in the registry. A "BadNameCacheEnabled" DWORD value of 0x0 will /disable/ the use of the "BadNameCacheList", even if the "BadNameCacheList" value does still exist in the registry.  This provides way to temporarily disable the list without actually renaming or deleting "BadNameCacheList" from the registry.
"BadNameCacheList" lists the server names. This is a multi string value, so multiple server names can be included. Server names added to this value will never timeout. For example, if you have a Microsoft server that you connect to, you can put its name in the "BadNameCacheList" value and the Novell Client will never try to resolve that name. The asterisk wildcard is supported. For example for the server named "SLES10SP4", the whole string can be provided in the registry or a wildcard can be used, such that an entry of "SLES10*" will block all the servers followed by SLES10, such as SLES10SP4, SLES10SP5, etc.
To enable the Bad Name Cache and add a server Bad Name Cache List:
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows to correct.
1. Run Registry Editor (REGEDT32.EXE).
2. Navigate to HKEY_LOCAL_MACHINE\Software\Novell\Client\Parameters
3. Enable the Bad Name Cache (Optional, see description above.)
a. From the Edit menu, select "New" and choose the "DWORD (32-bit) Value" option.
b. Enter BadNameCacheEnabled to name the new DWORD value
c. Right-click the new BadNameCacheEnabled value and choose the "Modify" option. Assign the value data of "1".
4. Add a server(s) to the Bad Name Cache List
a. From the Edit menu, select "New" and choose the "Multi-String Value" option.
b. Enter BadNameCacheList to name the new Multi-String value
c. Right-click the new BadNameCacheList value and choose the "Modify" option. Add the name of the server(s) as the value data. Place multiple entries on separate lines.
5. Choose OK and quit Registry Editor.
6. Shut down and restart Windows.

Additional Information

***Note: The above changes to the registry do not affect the BadAddress Cache Timeout setting in the client.  Currently, the BadAddress Cache Timeout cannot be turned off.  The acceptable values are 30-300 seconds.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7015227
  • Creation Date:18-JUN-14
  • Modified Date:23-OCT-14
    • NovellClient

Did this document solve your problem? Provide Feedback