any solution? please...
Have you tried re-installing the Agent? How many machines are you seeing this on?
when the McAfee Agent is getting new new policies and try to break it nothing happen...and the error was prompting...i think more than 100
Are you getting only one liner error 'Failed to communicate to the server' or any other error message?
Can we have snap below?
Here, we need to check couple of things.
1. Check the network communication from client to server and from server to client (with Netbios name,FQDN, IP address).
2. Make sure that agent ports (both agent to server communication port and agent to server secure communication port) are opened. This can be verified either from Telnet or by netstat.
3. How many client machines are not communicating? I will also suggest you to look into ePO server and see Apache service is running or not. If not then we should look there is port 443 is used by any application like IIS etc.
4. If still communication is failing then I will sugget you to post Agent and Mcscript.log file.
My McAfee Agent is now working properly and no error occured, after i restarted the service of ePO Server and disabled then enabled the port 443 on ePO my new policy is now refreshed and now working properly...
I get this same error on a group of machines with a new image. Not sure what to think we sysprep them and all but they keep giving the "fail to communicate with server" error. So the 90% of my machines work just fine and are all DHCP and confgured the same. The extremely weird part is the agents connect to the server for DAT files but do not get the policies or scheduled tasks. I setup a new task for Agent 4.5 Patch 2 but those machines with this error don't pull it down for install. What is the process for using netstat or telnet for testing connectivity on the assigned ports for the agent?
RickIA, I am having the same problem. It's not system wide, just a few machines here and there. Did you ever find out what was the problem?
I did. It was an agent duplicate guid problem. I ran a query called "Systems with High Sequence Errors" and it showed me the workstations that had the duplicate GUID problem. You select them go to Rogue Sensor and choose "Add to Sensor Blacklist" All of those machines the next time they communicate with the server will generate a new GUID.