Discussion Locked

NT 4.0 Workstation/Server and Novell cli

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a very interesting problem concerning Novell clients on Windows
NT (server and workstation and a 2000 Pro).

I have Novell Client 4.7 installed on an NT 4.0 workstation and a
Windows 2000 Pro and a Novell Client 4.6 installed on an NT 4.0 standalone server.

Whenever I reboot either of these 3 machines ALL user settings are lost.
But thats just the tip of the problem. I have found out that the reason
this happens is becuase the Novell clients are deleting the NT user account and creating a temp one of its own that it then uses and deletes on logout.

I keep creating the NT account on the workstation/server but it keeps getting deleted by the Novell client whenever I login.

Does anyone know why this is happening and how to stop it??

Chuck Brewster
Net Admin
Santa Barbara City College

11 replies

by erikdr

Check out the settings in the Workstation Manager part of both clients. There are all kinds of options for using an existing SAM account, creating one on the fly, having synced and unsynced passwords etc.
Apparently Novells default did not work well for your situation - you don't describe the details but usually I don't see a reason for keeping details of a local (SAM) user account when logging on to NetWare. All details, e.g. profile and preferences, should come from the NW server - either through the NT profile or through ZENworks starter pack. That's the philosophy behind it, and for many situations it is perfectly valid. Maybe not for uours but then you need to override some defaults...

Hope this helps,

/ The Netherlands

by sbowen

I run the 4.7 client with all of the patches on both NT4.0 Workstation and Windows 2000 Pro and have no problems. There are however, several patches out for the 4.7 client. You may want to look into applying thses patches as they fix an array of problems.

by imk

Chuck,

There have been a number of problems between Microsoft NT and Win2K and the Novell 4.71 client. I suggest you check this article on Microsoft:
http://support.microsoft.com/support/kb/articles/Q250/5/02.ASP?LN=EN-US&SD=gn&FR=0

Article ID Q250502, Cannot Access Novell UNC Share When You Run a Program as a Service

One thing to note is that if you want to change any file in the \winnt directory structure on Win2K you must be in Safe Mode as they have a 'new' system to prevent you from changing things permanently.

We've had some success with customers renaming a file call NWPROVAU.DLL on the Win2K machines. But supposedly Microsoft has a "fix" so you don't have to do this.

by swilliam

it sounds like you have the Dynamic Local User policy enabled in your WinNT User Policy Package. open nwadmin32 and look at the winnt user package associated to the affected users - if dynamic local user is selected, either uncheck it or reconfigureit to ensure that the volitile user option is not checked.

hope this helps!!

by schale

If you are using Z.E.N. works, there is an option that you can select where you can manage an existing account if it exists.

If this option was selected and you had a dynamic local user configured with a volitality set for something really small or 0 (I believe delete after logout) then your user accounts SHOULD be deleted because that is what you are asking for.

This discussion is closed to new replies.