Novell second logon box

[Red Squirrel]

One of our customers runs Novell (yeah I know, eww) and they have this problem that comes up at random, and it only affects certain accounts. They'll log in, authenticate, but then a 2nd logon box comes up for the local login. Sometimes you can put the admin password and it works, but 95% of the time they're stuck there until we log as admin and screw around with the settings and do a cleanup then it eventually goes away.

Anyone know what causes that, and how to fix it so that every user account can log in normally? (essentially we want everyone to log in automatically as a "user" account)

I don't have much info such as version of netware but if you require more info to help I can try to get it.

What I'd like to do is find a way to fix this through scripting and just push a script to all the PCs somehow.

 

[Nothinman]

Sometimes you can put the admin password and it works, but 95% of the time they're stuck there until we log as admin and screw around with the settings and do a cleanup then it eventually goes away.

What settings do you screw around with?

 

[Red Squirrel]

Usually under novel client, in tcp/ip settings. You can make it so it logs on as a certain user. It's not so much as "screwing around" more like "refreshing". Go through, make sure it's ok, then hit apply. Sometimes undo the settings and redo them, then apply. Othertimes we go and delete all the local users/profiles. But it seems to be hit or miss so don't think we're really doing the right thing. If I can find exactly what causes this and how to fix it then I can write a fix for it and mass deploy it (well get the L3 techs to do so, to follow processes properly etc).

 

[Red Squirrel]

I had some time to play around with this. Seems that when you play around with the user group memberships it can fix/break it. This one user had that issue at every workstation. I created a test user under same context, that user was ok. I checked for any differences, found that the user that it did not work had a different user group. I added the usergroup that is normally assigned. Fixed the issue. Though when I tried to break the test user to see if I can fix it the same way, it took a bit more playing around. So it's kinda weird.