When you say you ping the machine, do you mean the ping function inside ePO, or a command prompt ping from the OS?
The IP address shown in ePO is the last address reported back by that client - if the client's address has changed since its last communication then the IP that ePO knows will of course be out of date
Yeh i meant ping within the ePO, i probably should of mentioned that part. Again what happens is no response from the ping within the ePO, yet if you system ping the hostname..you get a response (different IP address of course), so which begs the question why ePO isnt updating? or am i missing something in my overview?
1 of 1 people found this helpful
In ePO, check the last updated time for one of these machines... has it updated in ePO recently? If not, you'd need to investigate at the client end to find out what's happening: the agent log is going to be the first place to start.
worked for a couple of the machines. Most of these particular machines are not even communicating with the ePO. Doing a hostname ping (in cmd prompt) gives me one IP address... but if I do nbtstat -A <ip from ping> it gives me a completely different hostname.
I ran the ping and nbtstat from the server ePO 4.5 is running from. Seems to be a DNS issue I'm guessing within AD.
Cheers for your help Joe.
Yup, sounds like a name resolution issue... not a lot ePO can do about that, I'm afraid
Check your DNS zones in AD. Pay particular attention to your reverse DNS zone. Make sure DHCP is updating DNS when IP addresses change.
Are you using/referencing the same DNS server on your ePO as you are on your client machines. It sounds as if you are using different servers, and they are not talking correctly.