It doesn't technically require the published hostname but if its internal hostname doesn't match some resolvable address with the public DNS system then it could be the source of your problems. It is ever fails to connect and the attempts to resolve it, the agent could get stuck with the wrong address. Usually I edit the published hostname but leave the IP blank. Letting DNS do the heavy lifting is usually the right way to go.
Well I don't have a published hostname, only a public IP associated to it.
The weird thing is that I connects once I installed the framepkg and gets all the policies/tasks/package. It's when I force to re connect again that it can't reach it. Maybe I'll try to set up a public DNS entry for it.
Does this agent handler needs to be a distributed repository as well ? Do I need to set up a public repository for agents outside of the network or is the public AH is enough ?
The problem is within the sitelist. The first connect updates it. You will need an externally addressable hostname and a published hostname. Likely the client is still attempting to resolve the internal name and it is coming up with unusable results.
I'm having the same issue. Prior to test my setting with an external machine, I have tested our published DNS name and ePO server-AH server and both of them worked pretty well.
The problem arised when I tested my setting with an external machine and I had exactly the same "Agent Failed to communicate with ePO Server" message.
Adding a published DNS to the agent handler seems to have solved my problem.