Is the AH showing up correctly in ePO and enabled ?
Also you need "AH -> ePO Server´s Agentcommunication port" setup in your firewall so that the AH is able to download the DATs from the masterrepository.
No repository setup is required and for the agent to AH communication the secure port is sufficient.
Yes on the Agent Handler showing up as active on our master ePO server. We also have the port open and the AH is getting the DAT from the master repository.
The problem is that the client is not able to update the DAT from the AH. It hangs at the McAfee Agent Updater and fails over to McAfee HTTP. The McAfee Agent performs the ASCI without any problems.
Please start the update process on the affected client and afterwards post the AGENT_%computername%.log.
Thanks metalhead but I created an SR ticket through McAfee Support. I sent them the MER data from one of clients, master ePO server, and Agent Handler. I do not like posting log files from our company to any forum if I can help it.
Note: I upgraded our Dev master ePO server and Agent Handler to ePO 4.5 Patch 4 (Hotfix 1). The ASCI from our clients outside our network is much much faster than when we were at ePO 4.5 Patch 3. Wished it would have fixed our DAT update problem.
I will keep you posted if I find out anything.
Perhaps you will get a clue on the problem yourself if you check the mentioned log.