Subject: | |
From: | |
Reply To: | |
Date: | Mon, 14 Apr 1997 15:53:00 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Uli asked......
> Hi everybody,
>
> some months ago this group was discussing a tool which was able to show
> the IP Adress of all sessions loged on.
> Does anybody know something about this thing or where to get it ?
>
> Thanks, Uli
>
> Reply to: mailto:[log in to unmask]
I use nettool.net.sys for this. A sample session follows.
--------------------------------------------
:nettool.net.sys
NETTOOL Version: B05082B3
Enter HELP HELP for an explanation of the help facility.
Enter HELP OPERATION for guidance on NETTOOL use.
Commands can be abbreviated, HELP keywords cannot.
Menu-specific commands for the ROOT:
RESOURCE CONFIG NAMEADDR PING STATUS NMDUMP
X25STAT X25CHECK IPCINT XPVAL XPPERF QVALNS
NSTEST LOOPINIT NSLOGON SOCKINFO filters
[1]>>>name
CACHE MAPPINGS ROUTING PATH filters
[2]NAMEADDR>>>cache
NAME DELNAME DELPATH LOCAL TOTALS
filters nodefilter sorting
[3]NAMEADDR.CACHE>>>name
AAMBERS.IDPA01.IDPA
In cache.
172.16.1.62 Path report 802 address :08000989A15B
ABONDE.IDPA01.IDPA
In cache.
192.23.1.207 Path report 802 address :0800099C6B56
ADEKETT.HSD01.IDPA
In cache.
172.16.1.161 Path report 802 address :080009433EF4
ALCOHOL.HSD01.IDPA
In cache.
172.16.1.124 Path report 802 address :080009AA2D1F
ASILVERMAN.IDPA01.IDPA
In cache.
192.23.1.216 Path report 802 address :0800099C4BEC
BCREBBS.IDPA01.IDPA
In cache.
192.23.1.175 Path report 802 address :080009482DCD
BDELL.IDPA01.IDPA
In cache.
192.23.1.162 Path report 802 address :0800093E5A89
BFAILOR.IDPA01.IDPA
In cache.
172.16.1.14 Path report 802 address :0800096A996E
BLEVY.IDPA01.US
In cache.
192.23.1.180 Path report 802 address :0800096AA947
BMALONIS.IDPA01.IDPA
In cache.
192.23.1.17 Path report 802 address :080009AADB1E
BMORGAN.IDPA01.IDPA
In cache.
192.23.1.169 Path report 802 address :0800096AA92E
BROSE.IDPA01.IDPA
In cache.
192.23.1.5 Path report 802 address :0800098EAE4C
------------------ etc. etc. etc. ---------------------
As you can see, it is sorted by the node name from WRQ's HP3000 section.
It has been helpful when we have had a clash of IP addresss.
From looking at the list, it doesn't even seem that the user has had to
log on to the system. I know a few names from above don't use this
particular system.
/alan
[log in to unmask]
|
|
|