Bindery last-login info

2 views
Skip to first unread message

eng...@csc.canterbury.ac.nz

unread,
Sep 4, 1992, 1:37:47 AM9/4/92
to
A (tricky?) Novell technical question :

With SYSCON, under the "User Information" option, you can select
the "additional information" option. Amongst other things it
gives you the last login time/date of the selected user. This is
well and good.

What I want to know is how do you get this very information
(last login date) using the Bindery Services - i.e.
the INT 21H calls with the E3 function codes, esp. 3D (Read
Property Value). I am very familiar with these calls and have got
a lot of information from the bindery, but this last-login-time
eludes me. One would expect the relevant property (say
"LAST_LOGIN", or similar) to appear on the nice table on page
3-13 of the Bindery Services manual (Netware System Interface
Technical Overview) but there is nothing there remotely like it.
I have tried several combinations of potential strings in the
vain attempt of succeeding, but with no luck.

Help! (We are running V3.10)

Andrew Earl (ENG...@canterbury.ac.nz)

-- He who laughs last, laughs second-to-last next time. --

R.v.Kampen

unread,
Sep 11, 1992, 9:29:16 AM9/11/92
to
In article <1992Sep4....@csc.canterbury.ac.nz> eng...@csc.canterbury.ac.nz writes:
>A (tricky?) Novell technical question :
>
>With SYSCON, under the "User Information" option, you can select
>the "additional information" option. Amongst other things it
>gives you the last login time/date of the selected user. This is
>well and good.
>
>What I want to know is how do you get this very information
>(last login date) using the Bindery Services - i.e.
>the INT 21H calls with the E3 function codes, esp. 3D (Read
>Property Value). I am very familiar with these calls and have got
>a lot of information from the bindery, but this last-login-time
>eludes me. One would expect the relevant property (say
>"LAST_LOGIN", or similar) to appear on the nice table on page
>3-13 of the Bindery Services manual (Netware System Interface
>Technical Overview) but there is nothing there remotely like it.
>I have tried several combinations of potential strings in the
>vain attempt of succeeding, but with no luck.

it is stored in the LOGIN_CONTROL property
format :
offset 00-02 : account expiration date (format YYMMDD), 000000 if none
03 : ff= account disabled
04-06 : password expiration date YYMMDD, 000000 if none
07 : grace logins remaining, ff=no limit
08 : ????
09 : days between forced password change
0a : grace logins allowed, ff=no limit
0b : minimum password length
0c : ??
0d : maximum # concurrent connections (ff=no maximum)
0e - 37 : timerestrictions (bitmap)
38 - 3d : last login (YYMMDDHHMMSS)
3e : bit0 : user not allowed to change password
3f - 49 ??
4a - 55 : last intruder address (4:6:2 bytes)

the rest I haven't figured out yet, if any body else got more
info on other properties please let me know

willem (win...@dutiws.tudelft.nl or wil...@dutikos.tudelft.nl)

boB

unread,
Sep 13, 1992, 2:05:35 AM9/13/92
to
In article <20...@dutiws.tudelft.nl> win...@dutiws.tudelft.nl (R.v.Kampen) writes:
>it is stored in the LOGIN_CONTROL property
> format :
>offset 00-02 : account expiration date (format YYMMDD), 000000 if none
>03 : ff= account disabled
>04-06 : password expiration date YYMMDD, 000000 if none
>07 : grace logins remaining, ff=no limit
>08 : ????
>09 : days between forced password change
>0a : grace logins allowed, ff=no limit
>0b : minimum password length
>0c : ??
>0d : maximum # concurrent connections (ff=no maximum)
>0e - 37 : timerestrictions (bitmap)
>38 - 3d : last login (YYMMDDHHMMSS)
>3e : bit0 : user not allowed to change password
>3f - 49 ??
>4a - 55 : last intruder address (4:6:2 bytes)
>
>the rest I haven't figured out yet, if any body else got more
>info on other properties please let me know
>

got this info from novell tech support. i think i did about as well as you on
my own, but some are just hard to figure out. i had to break down and call.

ohh well

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Offset field size type
------ ----- ---- ----
0 Account Expiration DAte 3 bytes byte
3 account disabled flag 1 byte byte
4 password expire date 3bytes byte
7 grace logins remaining 1 byte byte
8 password expire interval 2bytes word
10 grace login reset value 1 byte byte
11 MIN password length 1 byte byte
12 max concurrent connections 2 bytes word
14 allowed login time bitmap 42 bytes byte
56 last login date and time 6 bytes byte
62 restriction flags` 1 byte byte
63 unused 1 byte byte
64 max disk usage in blocks 4 bytes long
68 bad login count 2 bytes word
70 next reset time (bad login) 4 bytes long
74 bad login address 12 bytes byte
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

hope it helps...

bob
--
Bob Hollinger <------------------------------------->
Wheaton College / B...@david.wheaton.edu \ Disclaimer:
CPO #1343 > uunet!tellab5!wheaton!Bob <
Wheaton, Il 60187-5593 \_____________________________________/ [CENSORED...]

Reply all
Reply to author
Forward
0 new messages