I have installed the Novell Login Client v4.83 SP1. Even without the service pack, I have been experiencing a *very* annoying problem when trying to login to my Netware 4.1 server. I type in the username and password and click OK (all the context and server settings are correct) and it begins to log in - then I get about .5 second glimpse of the blue screen of death and then XP reboots. The only way I can get access to the desktop is to click "Workstation Only". XP actually gets as far as authenticating the user because it shows up in Console Monitor.

Funny thing is, I could log in without any errors for about a day. Then suddenly - this. No software installs or anything.

Upon further inspection, Dr Watson reports it is locwin32.dll and others appearing to cause the access voilation. I have tried installing, reinstalling, deleting and changing settings - to no avail. There is nothing on novell about the problem, so I don't know where else to search for a solution.

Thanks for reading, and I hope someone can help :)

Thanks. Nick.

The file that you say that Dr. Watson is reporting as being the problem is Novell supplied DLL's used by Microsofts (and Borlands) Compiler. Along with it's counterpart locwin32.lib. And of course many other DLL's and LIB's. If you can see that the user is getting authenticated might lead you to beleive that the problem, as you noticed, some place else in the login process. If I was troubleshooting the problem I would try to figure out what is not causing the problem, and then work on what is left. Just as a quick check on the Netware client you could try loading an older version, say 4.81 and see if it has any effect, good or bad. Sorry, it is just hard for me to evaluate a problem if I am not sitting in front of it. Unless it is a known one fix type answer.

Would you beleive that I am getting the same error after a fresh, complete reinstall of Windows XP Pro. This is VERY bizzare!!

Any suggestions anyone??

If you are having the EXACT problem after a re-install of the WS's OS, then the only common denominators are the NW Client, the NW User Account, and the NIC. Not taking into account the WS's hardware because you say you can complete a startup with WS Only selected. Based on this information I would try a different NW account for logging in to , and/or installing a different version of the NW Client. As for the NIC, maybe it could either be not working properly as in not negotiating correctly. Which could be a speed or duplex issue. But I don't see this causing a reboot of the WS. That's all I have.

Sorta follow up.. Well after ages of backing up i deleted and reinstalled the SERVER. Next time I go to log in, works like a dream! THEN, I log out, down the server, restart it, set the right time and try and log in again, and you bet ya - XP Reboots. I cant think of any reasons for this happening.

I have found a way around the reboot - Login with "Workstation Only". Set WinXP to map root say the Public dir on every login. Client authenticates and no errors. Weird! (Thing is you have to log in workstation only every time.)