Highlighted
teejay58 Absent Member.
Absent Member.
1406 views

tracking a user from another tree

We have a situation where users that are not created or maintained in our tree, use our workstations to log into a server at another campus. Our server and the other campus's server are not synced, do not share edir data, etc. We set up contextless login and use the hosts file to enable a single user to log on at any campus.

We would like to keep a record of which netware userID logged onto our machine, as well as the time they logged in. Seems like it would have to be something that is triggered by the NW Client on our machine, that writes to the C: drive on our machine, etc. as the client is the only thing in this login process that we have control over.

For users that we do create, we can easily do this by running a DOS batch file when they login and echoing system variables to a text file. But I'm just stumped on how to do this for a user that is not ours. It's a rather large security hole, as we are relying on the other campuses to run their labs as well and as tight as we run ours.

Any assistance will be certainly appreciated.
Labels (1)
Tags (4)
0 Likes
3 Replies
Peter3 Absent Member.
Absent Member.

Re: tracking a user from another tree

The best way to do this would require a service so it records an entry
upon a login event. You'll need a custom applet.


--


Peter
eDirectory Rules!
http://www.DreamLAN.com
0 Likes
teejay58 Absent Member.
Absent Member.

Re: tracking a user from another tree

Thanks Peter. We were just looking at the event log and what it would take to create a custom event for this purpose. Is this what you are talking about? (We have XP workstations.)

Peter;1851314 wrote:
The best way to do this would require a service so it records an entry
upon a login event. You'll need a custom applet.


--


Peter
eDirectory Rules!
DreamLAN Network Consulting Ltd. - Leading Authority on eDirectory and LDAP technologies
0 Likes
Peter3 Absent Member.
Absent Member.

Re: tracking a user from another tree

From my view point, the /best/ way is to use a service since then the user
would not be able to bypass it or shut it down (unless they have local
admin rights, where all bets are off). Other than a service, the trick is
to find a way to trigger the running of an application or batch file -
that the user cannot bypass - upon login, and is NetWare-aware so it can
pick up the necessary info for logging. Off hand, I'm not aware of any but
Google could be your friend in this quest.


--


Peter
eDirectory Rules!
http://www.DreamLAN.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.