There is many variables that could come into play, every situation could be be vastly different. Some devices might not even respond to a ping sweep though and looking at traffic might be required to catch when they arp for say their gateway IP, etc.
Scanners can come in very handy in mapping out a network when you don't have access to managed switches or devices are quite - some will send out more noise then others and if busy network sometime there can be a lot of noise to go through if your just looking for devices on network. I would be hesitant to just connect some 2nd hand device to a production type network without first looking at its config or reset, etc. Or run a dhcp server on your laptop to give it an IP. If its something you bought off ebay or got 2nd hand can and not reset or console in, then I would connect it on an isolated network (say a laptop only with sniffer) and find its IP and then try to access interface from that IP, etc. Or you can boot it and see the timestamp on the lease and rule out your known devices, etc.
Angry ip scanner 3.4 mac#
If you know its dhcp, I would just look to dhcp leases - especially if you know the mac from the outside of the device for example or its unique hardware so you would notice it from the first 3 of the mac per a vendor lookup, or that its different from all your other dhcp clients. More than happy to discuss all the different ways that you could find an IP from a device in lots of different scenarios - since depending on the situation, different methodologies and or tools maybe be leveraged for the best way to get the information your seeking. But sure if don't know where the device is in the DC and its only unmanaged switches you can have issues tracking something down for sure.
If its a device you have your hands on you can always connect your laptop to the interface to sniff what its sending. While I agree that all networks are different and one tool might not be the best for a specific network.
0 kommentar(er)
