Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Resolving IP conflicts?
- Thread starter bsimms
- Start date
If you have access to a Linux box (probably works on most *nix) you can use arping -D <ip address> (detect duplicate addresses) for each address in your subnet (use a shell or PERL script). This will detect any duplicate responses to an ARP whohas request.
Then you can statically set the address to test by using the arp -s <ip address> <mac address>.
If you are stuck with Windows, then you can use SolarWinds to detect the duplicate host and possibly track it down. You can download eval versions of their software.
As far as the DHCP problem is concerned, the scenario that comes to mind that would cause that "bad address" error is that you have some statically addressed machines on your network that fall into the scope of the DHCP addresses assigned by the DHCP server. Once those are identified and the addresses changed, those errors should go away.
pansophic
Then you can statically set the address to test by using the arp -s <ip address> <mac address>.
If you are stuck with Windows, then you can use SolarWinds to detect the duplicate host and possibly track it down. You can download eval versions of their software.
As far as the DHCP problem is concerned, the scenario that comes to mind that would cause that "bad address" error is that you have some statically addressed machines on your network that fall into the scope of the DHCP addresses assigned by the DHCP server. Once those are identified and the addresses changed, those errors should go away.
pansophic
- Thread starter
- #3
TheOldMan346
IS-IT--Management
bsimms,
Just read this after responding to your other post. Now I understand the question.
Community strings are essentially passwords. The password/string will enable you to connect and have different capabilities on the device. If you supply the "read" password, you will be only be able to query the devices. If you supply the "write" password, you will be able to read, set and reset values in the device.
This link defines it in greater detail.
Since many vendors use a default of "public", start with that. If that does not work, try to get in touch with whoever set up the network and see if he/she changed it.
Hope that helps.
The Old Man
Just read this after responding to your other post. Now I understand the question.
Community strings are essentially passwords. The password/string will enable you to connect and have different capabilities on the device. If you supply the "read" password, you will be only be able to query the devices. If you supply the "write" password, you will be able to read, set and reset values in the device.
This link defines it in greater detail.
Since many vendors use a default of "public", start with that. If that does not work, try to get in touch with whoever set up the network and see if he/she changed it.
Hope that helps.
The Old Man
- Status
Similar threads
- Locked
- Question
- Locked
- Question