cancel
Showing results for 
Search instead for 
Did you mean: 
biiro
Level 9
Report Inappropriate Content
Message 1 of 8

ePO 4.5 upgrade - client agent issues

Hi all,

New to the ePO orchestrator so please  bare with me on this.  At the moment we have 2 versions of ePO orchestrator running on 2 different boxes.  4.0 is running on an older box which is connected to our old LDAP domain database.  However, the new version we are using, 4.5, is connected to active directory and getting it's information from within that AD structure.  Now, the problem being, 4.5 is saying I have 530 odd machines NOT syncing with 4.5, however everytime I try to deploy the agent to these machines it fails to connect or just times out.

Out of those 530 odd machines I can see thats active, ePO is displaying the wrong information for that machine.  Here's an example, lets say that a desktop box called "userpc1" is being displayed in that list and ePO is saying the IP address is 10.2.4.100.  When I ping that IP address, it bounces and times out, however when I ping the hostname of the machine I get an active response.  Running nbtstat shows me that yes the machines active, but has a COMPLETELY different IP address to what ePO is showing.  This seems to be happening for most of the machines which are active.

I'm not 100% sure whats going on, however I'm thinking it might be a combination of old machines in AD which need to be removed or...there is an issue with DNS somewhere along the lines. 

Would be interesting to hear advice from some of the folk on here, normally able to find answers to most of my questions already, but this one has me stumped!

7 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 8

Re: ePO 4.5 upgrade - client agent issues

Hi...

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

Thanks -

Joe

biiro
Level 9
Report Inappropriate Content
Message 3 of 8

Re: ePO 4.5 upgrade - client agent issues

Thanks Joe,

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?

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 8

Re: ePO 4.5 upgrade - client agent issues

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.

HTH -

Joe

biiro
Level 9
Report Inappropriate Content
Message 5 of 8

Re: ePO 4.5 upgrade - client agent issues

Joe,

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.

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 8

Re: ePO 4.5 upgrade - client agent issues

Yup, sounds like a name resolution issue... not a lot ePO can do about that, I'm afraid

Regards -

Joe

plattr
Level 7
Report Inappropriate Content
Message 7 of 8

Re: ePO 4.5 upgrade - client agent issues

Check your DNS zones in AD. Pay particular attention to your reverse DNS zone. Make sure DHCP is updating DNS when IP addresses change.

Vargas
Level 7
Report Inappropriate Content
Message 8 of 8

Re: ePO 4.5 upgrade - client agent issues

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.