We are currently trying to deploy an Agent Handler on a different network of ours. We HAVE NOT made the ePO live, epo is working on private IP addresses, However since the Agent Handler has LIVE IP address, it will come through Internet to access the ePO server. We have done the following NATTING.
NATTING INFORMATION that is done as below and firewall rules are also working
MCAFEEEPO-1 (221.120.x.x) 8081 ---> AgentHandler (182.190.x.x) 8081
MCAFEEEPO-1 (221.120.x.x) 80 <---> AgentHandler (182.190.x.x) 80
AgentHandler (182.190.x.x) 8443 <---> MCAFEEEPO-1 (221.120.x.x) 8443
AgentHandler (182.190.x.x) 8444 <---> MCAFEEEPO-1 (221.120.x.x) 8444
AgentHandler (182.190.x.x) 1433 <---> MCAFEEEPO-1 (221.120.x.x) 1433
What We have Done
We have the following private IP addresses for EPO:
10.254.158.72 (NLB IP for ePO Application)
10.254.158.85 (NLB IP for MSSQL DATABASE)
We have used FRAMEPACKAGE to install on Agent Handler so its also listed in Managed Systems, When we right click and select ABOUT on Agent, it shows that it has the following ePO Server/Agent handler
and when we click pull policies and enforce policies, Agent shows that Communication with ePO server failed. I am assuming it is happending because when LIVE Agent Handler System tries to connect to 10.254.158.72 it cant find that private IP address and thus communication fails. Instead we should use 221.120.x.x instead of 10.254.158.72.
To address this change of IP address, we have Extracted FramePackage, edited the IP address from 10.254.158.72 to 221.120.x.x , installation of agent is successful, but agent doesnt gets registered, NO GUID is created and properties of agent shows BLANK GUID, means its not working.
How we can make the change to LIVE IP address for ePO server on Agent Handler/Agent so it can communicate back to ePO server with Natted Environment.
We are badly stuck at this point and need assistance.....