I have been working on this issue since September 29th withsome success.
Edison Ortiz has recommended re-installing licensing, which I plan to do
this weekend if no one has a better answer by then. I have three posts on
Novell forums going back to that time, but they have grown cold, so I am
re-posting. Most clients were 4.91SP2,IP only when this all started. I
might mention, I have two Windows 98 3.40 clients who haven't been
affected yet.

The following is a listing of some of the errors we have encountered and
corrections we have taken. Currently about 20% of the users have
encountered a problem and I have installed all possible client patces,
plus the one beta mentioned below. I have also gone into the registry on
three users and added a dword as mentioned below: Originally a few users
were getting:
Login-LGNWT32.dll-470: The specified drive mapping is an invalid path.
This leads to a NW6.0SP path that has worked for years. Now some are
getting no errors but when they try a shortcut to that server is cannot
find it and when you look in windows explorer they cannot connect.
Rebooting usually corrects. Sometimes they get: "Novel Security
Message": connection to the server was terminated. try workstation
only..... However just putting the password in again the logon works
fine. At one point I clicked on tree in advanced, it found it after a
while, but when I clicked on context it said: "No context found in tree
lorch". Rebooted the servers at this point NW6.0SP5 & NW6.5SP3

Then I installed "C" patch and all the Post patchestches I could find
after "C" on my computer.
Rebooted fine the first time, but got this the second time: LOGIN-
LGNWNT32.DLL-430: The following drive mapping operation could not be
completed.
[O:=\\ABRAM\DOCS\]
The error code was 8819.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[J:=\\ABRAM\BOSS\MAS90\]
The error code was 8819.
Tony Pedretti recommended the beta patch below:
http://support.novell.com/filefinder/20609/beta.html
Installed this patch even though it was beta and it seemed to help. (ie
20% login errors instead of 80%)
--------------------------------------------------------------------------
-----------------------------
We have LazycloseOff=1 in our windows logon.vbs

I put the DA servers IP number in as default server

I tried using:
Map X:=.volume-objet.path yesterday it worked but didn't help

No Zen

Turned off Bad Address Cache in advanced properties on my computer, no
help.

We are almost 100% Dell with OEM windows Pro SP2 fully patched. When we
install the novell client it is custom Ip only, remove IPX if present and
deselect NMAS.
On my computer, Protocol comes up as NDS, Host File, DNS, SCP, DHCP

This is from my workstation for slpinfo /a:

************************************************** ***
*** Novell Client for Windows NT ***
*** Service Location Diagnostics ***
************************************************** ***

SLP Version: 4.91.3.0
SLP Start Time: 4:15:13pm 10/3/2006
Last I/O: 8:04:42am 10/4/2006
Total Packets: Out: 71 In: 41
Total Bytes: Out: 5670 In: 1127


SLP Operational Parameters Values
------------------------------- ------------
Static Scopes YES
Static Directory Agents NO
Active Discovery YES
Use Broadcast for SLP Multicast NO
Use DHCP for SLP YES
SLP Maximum Transmission Unit 1400 bytes
SLP Multicast Radius 4 hops


SLP Timers Values
------------------------------------- ------------
Give Up on Requests to SAs 15 seconds
Close Idle TCP Connections 5 minutes
Cache SLP Replies 1 minutes
SLP Default Registration Lifetime 10800 seconds
Wait Before Giving Up on DA 5 seconds
Wait Before Registering on Passive DA 1-2 seconds


Scope List Source(s)
---------------------------------------- ------------
scope1 CNFG,DHCP


DA IP Address Source(s) State Version Local Interface Scope(s)
--------------- --------- ----- ------- --------------- ---------
------
10.16.148.21 DHCP UP SLPV2 10.16.148.42 Scope1


Local Interface 10.16.148.42
---------------------------------
Operational State: UP
Operating Mode(s): MCAST,STATIC-DA,DHCP-MANDATORY-SCOPES
SA/UA Scopes: scope1
Last I/O: 8:04:42am 10/4/2006
Total Packets: Out: 71 In: 41
Total Bytes: Out: 5670 In: 1127
Last Addr Out: 10.16.148.21
Last Addr In: 10.16.148.21
--------------------------------------------------------------------------
----------

What is strange is that if you click on tree, then context and then
server, sometimes it shows up with a Context? for the context or certain
servers. Different each time and for different users.
Not convinced yet that a Windows Security update didn't submarine Novell
logins.
--------------------------------------------------------------------------
----------
The error code was 8819.

This error code indicates you have a licensing problem. Please
troubleshoot your license consumption and post
back if you need further help.

--
Edison Ortiz

Edison:
I kinda supsect that so I checked it out, currently using 71 of 75
licenses for NW6.0 and 71 of 85 for NW6.5??
Should be OK, right?

Sometimes users don't even see an error on Novell login but cannot
connect to the NW6.0 server even though it says
authenticated on the Red "N".

I followed TID 10022465 to load dsrepair advanced and say yes to Schema,
no errors.

We are getting new users now who get logon errors.. Still wondering if it
might be something in the permissions. One user that i didn't have the
new client on yet got this error:

You are attached to server ABRAM.
PUFF
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[INS S1:=PUFF/SYS:\LOGIN]
The error code was 8884.
PUFF
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[INS S2:=PUFF/SYS:\PUBLIC]
The error code was 8884.
PUFF
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[F:=\\PUFF\SYS\]
The error code was 8884.
LOGIN-LGNWNT32.DLL-470: The specified drive mapping is an invalid path:
(H:=ABRAM/PUFF_WORK:USERS\LORRAINE)
Drive O: = ABRAM_DOCS: \
Drive J: = ABRAM_BOSS: \MAS90

I installed the "C" patch from server Puff and when I tried to run the
beta patch I mentioned she got:
\\Puff is not accessible. You might not have permissions to use this
network resource. Contact..... The network name cannot be found.

So I logged in as myself and was able to run the patch. On first attempt
for her to login as herself she got "Connection to the Server was
termininated". She retyped her password and after a long wait she logged
in successfully.


Now two of the engineers that I have already updated the client on are
still getting those errors:
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[O:=ABRAM/DOCS:\]
The error code was 8819.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[J:=ABRAM/BOSS:\MAS90\]
The error code was 8819.

--------------------------------------------------------------------------
See http://support.novell.com/cgi-bin/se...i?10091670.htm

--
Edison Ortiz

Edison: My computer had that DWord value. If anyone gets the 8884 error
I now have a reg file.
--------------------------------------------------------------------------
-
Yesterday I added Public with Browse rights as a trustee of the Group
Everyone, it had root already. I don't know if that will help or not.
__________________________________________________ ________________________
_


New error on Chastity Hedges:
LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 15 (8819)

New error - Peter Jam
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[O:=ABRAM/DOCS:\]
The error code was 8819.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[J:=ABRAM/BOSS:\MAS90\]
The error code was 8819.

New Error - John Gilliland
Authenticating to server ABRAM.
LOGIN-LGNWNT32.DLL-470: The specified drive mapping is an invalid path:
(O:=ABRAM/DOCS:\)
LOGIN-LGNWNT32.DLL-470: The specified drive mapping is an invalid path:
(J:=ABRAM/BOSS:\MAS90\)

New error 10-16
LOGIN-LGNWNT32.DLL-923