8884 error in login script mapping to available server

  • 3606879
  • 12-Jul-2007
  • 16-Mar-2012

Environment

Novell Client 4.83 SP2 for Windows Nt/2000/XP
Novell Client 4.9 SP1 for Windows Nt/2000/XP

Situation

8884 error in login script mapping to available server
NAL Objects fail to launch
Novell Client 4.9 SP2 for Windows Nt/2000/XP
Server is known to be up and running but client fails to login or map to it for 5 minutes after boot up
Traces show the clients successfully resolve the server and volume objects, and when they read the network address attribute they get the proper IP address for the server. SLP is returning the proper Address for the server but clients never attempt to connect on port 524 to that address.

Resolution

The Nal problem is fixed in the Zen 4 updates as of December 2004, problem has not been verified as existing in Zen 6.5

FIX for Non-Nal / Zenworks related problems with Bad Address or Bad Name Cache is to either find out WHY the server(s) is getting put in the cache
OR
to disable them completely.

For 4.9 SP1a and before, you can disable the Bad Name Cache with the setting in the client advanced properties and disable the Bad Address Cache with the following Registry, and setting then the problem goes away.
HKLM\System\CurrentControlSet\Services\Netware Workstation\Parameters
Create a Dword value called BadAddressCacheTimeout and set the value to 0

On 4.9 SP2 clients and beyond you do not need to set the registry key, you can set the Bad Address Cache off in the advanced client settings
Bad Address Cache Timeout = 0

Additional Information

Server address is getting put in the bad address cache on the client , which by default lasts for 5 minutes. There are 3 things that are being tracked down on this problem:

1) workstation manager is running before the client login and it may be causing the address to get cached as bad
2) the user object has that server set as their default server in the user object attributes
3) the server is registered in DNS and the client did also resolve it via DNS and we see that there is an attempt to connect to the server over PORT 445 which is the MS AD port.

Formerly known as TID# 10091670

Feedback service temporarily unavailable. For content questions or problems, please contact Support.