Dec 092017
| Dump out a Netware 2.12 server’s account data to a text file. This is a very handy utility for network supervisors. | |||
|---|---|---|---|
| File Name | File Size | Zip Size | Zip Type |
| ACCTDATA.EXE | 36098 | 21563 | deflated |
| NET$ADDR.DAT | 45 | 34 | deflated |
| README.TXT | 1718 | 755 | deflated |
Download File ACDATA.ZIP Here
Contents of the README.TXT file
08/15/89
ACCTDATA is a program I wrote to dump out the NET$ACCT.DAT file.
It needs to be able to find NET$ACCT.DAT, either on a search drive or in
the current directory. (NetWare creates the NET$ACCT.DAT file in the
SYS:SYSTEM directory.) A second file, NET$ADDR.DAT, is read to provide
logical names for physical addresses. If no NET$ADDR.DAT is present, the
physical addresses are displayed. The NET$ADDR.DAT layout is presented at
the end of this file. ACCTDATA should be run on the same server that the
NET$ACCT.DAT file was created by, so the server and client names can be looked
up in the bindery. ACCTDATA /? echos the syntax to the screen.
Normally output is sent to the console, 1 screen at a time. The /P
switch will override this and cause the output to formatted for and sent to
LPT1.
All our servers are running 2.12, so that is the only environment it
has been tested under.
NET$ADDR.DAT Layout:
Field Offset Length
------------------------------
Network 0 8 (padded with leading zeros, if necessary)
Colon 8 1
Node 9 12 (padded with leading zeros, if necessary)
Colon 21 1
Name 22 21 (padded with trailing spaces, if necessary)
NET$ADDR.DAT is the same file that is used by my USERS program, which
is also on NOVSOFT. So if you have created it for USERS, just make
sure it is on a search drive or in the current directory when running
ACCTDATA. A sample NET$ADDR.DAT is included in the ZIP file.
Tim Schwab (76344,1533)
eof
ACCTDATA is a program I wrote to dump out the NET$ACCT.DAT file.
It needs to be able to find NET$ACCT.DAT, either on a search drive or in
the current directory. (NetWare creates the NET$ACCT.DAT file in the
SYS:SYSTEM directory.) A second file, NET$ADDR.DAT, is read to provide
logical names for physical addresses. If no NET$ADDR.DAT is present, the
physical addresses are displayed. The NET$ADDR.DAT layout is presented at
the end of this file. ACCTDATA should be run on the same server that the
NET$ACCT.DAT file was created by, so the server and client names can be looked
up in the bindery. ACCTDATA /? echos the syntax to the screen.
Normally output is sent to the console, 1 screen at a time. The /P
switch will override this and cause the output to formatted for and sent to
LPT1.
All our servers are running 2.12, so that is the only environment it
has been tested under.
NET$ADDR.DAT Layout:
Field Offset Length
------------------------------
Network 0 8 (padded with leading zeros, if necessary)
Colon 8 1
Node 9 12 (padded with leading zeros, if necessary)
Colon 21 1
Name 22 21 (padded with trailing spaces, if necessary)
NET$ADDR.DAT is the same file that is used by my USERS program, which
is also on NOVSOFT. So if you have created it for USERS, just make
sure it is on a search drive or in the current directory when running
ACCTDATA. A sample NET$ADDR.DAT is included in the ZIP file.
Tim Schwab (76344,1533)
eof
December 9, 2017
Add comments