Sounds like the machines IP adress has been re-assigned to another device, or you may have a DNS./name resolution issue. So machine1 used to have an ip of 10.132.22.22, it has been off the network for sometime and its ip has been reassigned to machine2 machine1 is in the query, however during discovery it sees the ip of 10.132.22.22 as alive. etc... This all controlled by the discovery option Configure | Agent Discovery Options.
Discovery methods: Indicates how the agent is discovered.
IP address: Uses the core database to retrieve the computer's stored IP address.
Domain Name Service (DNS): Resolves the computer's ID name with the DNS server when verifying the remote control agent. If you do not have a DNS server, clear this option.
Default is IP then DNS. Clear as mud
Thanks for the reply, i get what your saying with DNS etc, and it makes sense that machines have picked up other machines addresses, i just wasn't sure how from the console window the agents were contacted to determine if they were up or not ... does it simply pole the device using the device name (resolving using dns obviously) or does it use the last logged IP address for the device within the console itself?
Ive tried pinging the devices from the core and my own machine (console) and neither come back, so im assuming it must use the last logged address (last known address in the database)
Cheers - Ben
If you have not changed the discover options then it uses the core database to retrieve the computer's stored IP address. So it is grabbing the ip address from the DB record of the computer.