I've recently been given the task of going over the ESET Remote Admin Console and making sure all hosts are up to date. There are a few that are messing with me though. One client PC is reporting (under remote install tab) that it hasn't connected in two months. So I right clicked on it and chose Windows Push Install. Under Install Tasks tab I saw that it said the operation was successful. I even remoted into that particular client and checked on that end and ESET says it is up to date. Every day ESET still reports that this client hasn't connected in two months. It was then that I noticed that ESET lists that client IP address as 2.196 when in fact that machine has an IP of 2.180. So is this reason that ESET thinks this client hasn't connected in two months when it actually has? Why is it reporting the wrong IP address for this machine? I can't ping the 2.196 address so I have no idea what PC has this address now. I don't have access to the DHCP server so I'm not sure how to find out what PC had the 2.196 IP two months ago since I assume that's the one that actually hasn't checked in for two months. Any ideas what I should do? This software is still new to me so I don't know why it's telling me this machine hasn't checked in for so long when it clearly has.