Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Last Login" not being updated.

Status
Not open for further replies.

BrianH1

MIS
Aug 29, 2002
82
GB
I have been given the task of deleting old users from the system. I have been given a report of all the users who have not logged into the network in three months. This was produced using nlist with "Last Login LT 01/01/2003"

The problem is, when I tried to delete one users home drive, several of the files were in use. I checked in NWAdmin and the last login date is back in 2002, however, on the console, the user is shown under current connections and has logged in each morning for the last three days I've been looking at this problem.

All the clients are either NT/2000 (using 4.83SP2) or 95 (3.32SP1) and the servers are a mix of 4.11 and 5.1 with DS versions 6.10, 6.11, 8.38 and 8.59

Time is synchronised and DS is also synchronising fine.

I have since found several other accounts where this field does not seem to be updating, but it's by no means every user. Users in question have rights to modify the field.

Any ideas appreciated.
 
I don't know about clearing the login box, but I do know that you can use NWAdmin to disable to accounts so no one who happens to know the old user's password or services that use the accounts can use them to actively login.

Open up the tree until you find the user accounts, Right Click and choose Details. On the Login Restrictions tab you will find "Account Disabled". Click there. Then it's a matter of clicking OK and closing NWAdmin when you're done. The accounts should be prevented from logging in as long as that check mark is there so you can delete their drives to your heart's content.

Alternatively, it could be a script problem that is forcing automatic network drive mappings on the windows clients. Go to Windows Explorer on each machine, right click the mapped drive and choose disconnect. It's a little labor intensive, but probably what happened was someone, when doing the original mapping, choose the "Reconnect at Login" option.

Hope that helps. Catadmin - MCSA
 
Thanks for the response, Catadmin.

I don't think I explained my problem very well.

I don't want to delete the accounts that are in use. What I want to be able to do is rely on the "Last login" field in the Login Restrictions shown in NWadmin. This is not being updated when users login, so when I run a report on the users that have not logged in within three months, many active users are being shown.

I believe this started happening when the server that most of these users authenticate to was upgraded to netware 5 from netware 4.
 
Oh, sorry. I saw that comment about attempting to delete a user's drive and misunderstood. My bad.

Have you checked Novell's support site to see if they've hit that problem yet? Catadmin - MCSA
 
Has DSREPAIR come up with any errors? I would certainly consider standardising your DS and Service Pack version across NetWare 4.11 and 5.1 to the latest versions for each - servers work better when things are the same, almost like us humans! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
DS repair runs fine on all the servers in the tree, the only messages being given are "Deleting unused property Synchronised up to..."

I've checked Novell, nothing there.

There is a plan to move all the servers to Netware 5 so we can standardise on one DS version, I agree that this would be the ideal first step but the company that we support are quite tight, there are servers out there from Proliant 1500s to ML370 G2s. The do however want to remove IPX from the network and without upgrading the servers and moving away from 4.11 there's no way that can happen.
 
Since my last post, I've installed SP6 on the machine, and all indications are that the problem has gone. Thanks to all who replied...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top