Re: Agents cannot communicate with epo-server - SOLVED!
The problem appears to be related to the EPO 3.6.1 server public keys. In fact, McAfee support had to replace the entire contents of my \Program Files\McAfee\ePO\3.6.1\DB\Keystore folder in order for 18.104.22.1683 agents to communicate back to the EPO 3.6.1 server running on Windows 2003 Server SP2.
After this task was performed, the agents started communicating with the server, the "Last Updated" field started populating, the TIME_WAIT connections on the server went away, the TCP checksum errors (failed encrypted SPIPE communications) went away, and agents started enforcing policies and tasks!
After doing a binary comparison of those public keys replaced by McAfee Support, and the ones installed by the EPO 3.6.1 installer(s), the only 3 files that changed were: srpubkey.bin, srseckey.bin and srseckey.old. So these seem to be key (pun intended).
For those experiencing similar agent-to-server communication problems with EPO 3.6.1 running on Windows 2003 Server SP2, call McAfee Support immediately and demand they replace your \Keystore keys on the server!
I've lost 4+ days of productivity due to this mess, but luckily, it was fixed prior to taking the inneviatable rebuild server from scratch route.
As of this time, no KB article addresses this solution.