Patriot,
Here are the results:
Code: Select all
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
# nbtscan -t 10000 -q -r -s "|" 10.0.0.0/8
#
#
# nbtscan -t 5000 -q -r -s "|" 10.1.0.0/16
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.70|SHELLY-PC |<server>|<unknown>|0c-ee-e6-b0-88-f2
#
#
# nbtscan -t 2000 -q -r -s "|" 10.1.1.0/24
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.70|SHELLY-PC |<server>|<unknown>|0c-ee-e6-b0-88-f2
nbtscan -t 5000 -q -r -s "|" 10.1.0.0/16 this is hit and miss don't always find the wireless windows7 laptops, any less than 3000 don't find anything at all
the nbtscan -t 2000 -q -r -s "|" 10.1.1.0/24 gives the best result, I changed the -t 1000, 500, 250, 125
Code: Select all
nbtscan -t 1000 -q -r -s "|" 10.1.1.0/24
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.70|SHELLY-PC |<server>|<unknown>|0c-ee-e6-b0-88-f2
#
#
# nbtscan -t 500 -q -r -s "|" 10.1.1.0/24
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.70|SHELLY-PC |<server>|<unknown>|0c-ee-e6-b0-88-f2
#
#
# nbtscan -t 250 -q -r -s "|" 10.1.1.0/24
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.70|SHELLY-PC |<server>|<unknown>|0c-ee-e6-b0-88-f2
#
#
# nbtscan -t 125 -q -r -s "|" 10.1.1.0/24
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
set -t 125 the windows7 laptop drops out, the 10.1.1.0/24 seems to be more of the deciding factor regardless of time.
hope this is of some help to you
Geoffrey
Edit: nbtscan -t from 3000-5000 on 10.1.0.0/16 this is hit and miss don't always find windows7 laptop [10.1.1.70|SHELLY-PC |<server>|<unknown>|0c-ee-e6-b0-88-f2], it may be that the wireless needs more time
terminal output for lameSMBxplorer reads:
# lameSMBxplorer
Network(s):
10.0.0.0/8
ScanNBT 10.0.0.0/8:
Edit: some more test
# nbtscan -t 10000 -q -r -s "|" 10.0.0.0/8
# nbtscan -t 10000 -q -r -s "|" 10.0.0.0/16
# nbtscan -t 10000 -q -r -s "|" 10.0.0.0/24
it appears that it don't like 10.0.0.0
# nbtscan -t 5000 -q -r -s "|" 10.1.0.0/16
10.1.1.4|THEBOX |<server>|<unknown>|00-19-db-a1-e0-aa
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
# nbtscan -t 6000 -q -r -s "|" 10.1.0.0/16
10.1.1.4|THEBOX |<server>|<unknown>|00-19-db-a1-e0-aa
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.9|SKYES-PC |<server>|<unknown>|0c-ee-e6-b0-8c-73
10.1.0.0/16 works best above 5000
# nbtscan -t 1000 -q -r -s "|" 10.1.0.0/24
# nbtscan -t 5000 -q -r -s "|" 10.1.0.0/24
# nbtscan -t 10000 -q -r -s "|" 10.1.0.0/24
# nbtscan -t 1000 -q -r -s "|" 10.1.1.0/24
10.1.1.4|THEBOX |<server>|<unknown>|00-19-db-a1-e0-aa
10.1.1.3|REPOTEC |<server>|REPOTEC |00-00-00-00-00-00
10.1.1.10|PUPPYPC |<server>|PUPPYPC |00-00-00-00-00-00
10.1.1.9|SKYES-PC |<server>|<unknown>|0c-ee-e6-b0-8c-73
10.1.0.0/24 is not a go
10.1.1.0/24 is fine
Hope this don't confuse you , it's starting to with me