Good morning,

So I have ran into this issue twice now and I am wondering if anybody else has a solid work around. So, part of installing McAfee EPO is having SQL installed. The two communicate over port 1434. However, regardless of what rules I build, I cannot get McAfee to communicate over UDP 1434 without disabling firewalls through GPO, disabling firewalls locally, AND disabling the firewall service on the local machine. Its really overkill. Again, setting TCP/UDP rules allowing all traffic over 1434 has not worked. The McAfee KB on the subject, is good, but doesn’t mention this at all. Any suggestions or thoughts on what may be the issue would be helpful. Not an issue due to our network config, just seems odd that a security suite would require firewalls to be totally disabled in order to even install.

7 Spice ups

According to the link below you need two ports for SQL to traverse the firewall:

SQL Server

Default port Protocol Traffic direction

1433 TCP Inbound connection from the ePO server or Agent Handler

1434 UDP Inbound connection from the ePO server or Agent Handler

ePO server

Port Default Description Traffic direction

SQL Server TCP port 1433 TCP port used to communicate with the SQL Server. This port is specified or determined automatically during the setup process.

Outbound connection from the ePO server or Agent Handler to the SQL Server.

SQL Server UDP port 1434 UDP port used to request the TCP port that the SQL instance hosting the ePO database is using.

Outbound connection from the ePO server or Agent Handler to the SQL Server.

ePolicy Orchestrator port requirements for firewall traffic: https://kc.mcafee.com/corporate/index?page=content&id=KB66797

2 Spice ups