Client32 4.9SP2c - Second login prompt

[ByteEater]

Netware 5.0 SP6a
Ds.nlm v7.51
No Directory Agent

Windows XP Pro SP1 & SP2
Client32 4.90 SP2c including 3 dec. newest 3 updates
Problem is also occurring with 4.91 Beta
Client32 is installed with IP & IPX compatibility (We still have some IPX Print Q's left and 1 Netware 3.12 server)
No NMAS, no NOCI and no NETIDENTIFY where installed with the client. I used ACU and a custom install script.

Right after clicking OK on the regular Novell login box, another one appears right away with only username and password fields and is entitled with a server name witch is not the default server that is in the client32
settings. It's like it's asking me for a bindery authentification. Note that the second login prompt is a Novell login box, not Microsoft. Both NDS and ADS passwords are synchronized. Whatever credential you put in the second box fails to authentify. Login script result lists the following error.

LOGIN-LGNWNT32.DLL-870: An unknown error was returned during LOGIN’s attempt Error code: 89F0.
LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 15(8801).

It would take 2 full pages to list all of what I tried to fix the problem but it was mainly limited to playing in Advanced settings in the client32 configuration. In a couple of cases, the problem disappeared and reversing the settings to original position didn’t reproduce the problem. Once the second login prompt disappeared, there was no way to bring it back!!! GONE If someone else has the same problem, we may compare notes and see if we can fix that without waiting after the Novell people. The main reason why I want 4.9SP2 to work is that we are soon deploying WinXP SP2 on 6800 computers. Euhh!

Thanks in advance!

 

[sstoppel]

It is likely the 3.12 server wanting you to authenticate. If you have a drive mapping to the 3.12 server or if the workstation is attaching to a print queue on it, that is the login. Launch syscon and make sure your passwords are in sync. There is a way to let 3.12 servers get authentication via the tree, but I forget how. Is upgrading that server an option?

 

[marvhuffaker]

Do you know which server it is trying to authenticate to on the second login prompt? Usually a bindery login box means that a DS connection couldn't be established.. so there could be something wrong with DS on that server, assuming it's a 4.11 or higher server.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[ByteEater]

I'm not trying to map or connect to the 3.12 at all and logon script does not refer to that box. Second login box refer to Netware 5 servers (not always the same) and the funny thing is that it is in the same Tree!!! When login, computer is trying to attach itself to the default server and then to a second one before mapping drives. In the logon script result window, I can see "Attached to server xxxx" and then the next line would be "Attached to server yyyy". That's when I don't get the second logon prompt. When I do get it though, the second line in the result is not there. That's the server I get prompted with the second logon box. Then in the result, I will see "Attached to server yyyy" after seeing the 2 errors:
LOGIN-LGNWNT32.DLL-870: An unknown error was returned during LOGIN’s attempt Error code: 89F0.
LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 15(8801).

I hope it makes sence to you the way I explain it.

I looks like it's trying to authenticate to the first server, then tries the second one without waiting for a OK from the first login attempt. So while it is trying to authenticate to the second one, it is probably already autheticated to the first one and can't attach to a second Netware ressource with the same credential. That's why the second logon box and that's why I can't login, using that second box.

WOW, I'm out of words to explain this!

Thanks for your replies!

 

[TheLad]

Searching for the 8801 part of the error code, it may be that the server in question is out of connections maybe? Or that particular server may have DS errors?

It may also be worth removing all printers from an affected workstation to see if that resolves the issue (although this is a shot in the dark as this has resolved quirky errors for me before!?!).

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------