Anyway - my question is, can anyone think of a good way of polling the subnets, we are currently NBTSTATing each possible IP address in each of our legal subnets, but this can take many hours in a sparsely populated subnet.
I saw the post on dhcpcmd, and that sparked my interest - but it still doesnt give me the hard coded addresses (we have a handful of them out there).

I hope this makes sense - any ideas ?

Thanks in advance
Mark

code:

---

$x=001
DO
 $ip = "192.168.201." + $x
 SHELL "PING $ip"
 $x=$x+1
UNTIL $x=256

---

Your example is kind of what we are doing (although ping takes an age to fail for a non existent ip address - even with timeout options wound down) we are just substituting nbtstat, which fails quicker if ip not present, and also gives us some extra information.

What I am thinking of is womething that would scan a range of ip addresses quickly - I have a gui product called wspingpro (from ipswitch) which does it, but I want a command line product. I have seen various subnet scanners used for simulating hackers - but I dont want to go near that sort of arena.

For instance a NBTSTAT -A for an address that is not active takes 13 seconds - to scan 10 subnets with one or two active ip addresses in each subnet would take about 9 hours. Something like WSPINGPR would take about 5 minutes.

Mark

I am using WINSDMP from the NTRESKIT, this dumps out the wins records from a given Server, in csv format, and appears to give me what I need.

I just pull out all of the 0 type records (which I think is workstation service) this gives me a list of around 650 PCs in about 45 seconds.

Obviously Printers etc which would have responded to a ping may not be talking to WINS, but its only PCs that interest me.

Have a look at the network tools on http://www.webattack.com/ - a quick search for ping came up with this nifty little utility: http://www.webattack.com/get/ipscan.shtml in their network scanner category.

See our site http://home.wanadoo.nl/scripting , which contains
a lot of scripts for making an inventory of software and hardware.

Those scripts contains mechanism to create dynamic and/or historical logs.
To prevent you doesn't catch them all you can reboot (= all user will be
logged off) server and after each loggin on you can get the wanted
information.
Greetings.

btw: symbol on our homepage has been linked to related http://kixtart.org topic.