cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

Added a Secondary Domain Controller

Jump to solution

We finally added a secondary DC to aid in redundancy. Every since then, our mcafee agents are no longer communicating with the ePO server (which is installed on our primary DC). Both the primary and secondary DC's have DNS. The ePO version is 5.1, primary DC is server 2008 R2 and secondary DC is server 2012 R2. Does ePO need to be installed on the secondary DC for this to work? In need of some guidance please. I know having ePO on a DC is NOT recommended but this is how it is right now. I am working on putting ePO on a different server but that might be months down the road.

1 Solution

Accepted Solutions
Highlighted

Re: Added a Secondary Domain Controller

Jump to solution

have you reviewed the agent logs on an affected endpoint to attempt to ascertain why they are no connecting to the ePO server? By default on a 32-bit machine this will be C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\DB\Agent_<computername>.log and for 64-bit systems C:\ProgramData\McAfee\Common Framework\DB\Agent_<computername>.log.

I can only assume that there hasn't been any changes to the DC that has the ePO installed e.g. IPv6 enabled, new network interface installed, host name change, network routes/firewalls etc. McAfee Agent attempts to connect to the ePO in the order of last known IP address, DNS name, or NetBIOS name, so in theory if you haven't changed the IP address of your ePO then endpoints should still be able to communicate.

You might also want to check that there is no conflicts with a possible new component installed on your existing DC and the ePO communication ports.

HTH,

Mick

View solution in original post

2 Replies
Highlighted

Re: Added a Secondary Domain Controller

Jump to solution

have you reviewed the agent logs on an affected endpoint to attempt to ascertain why they are no connecting to the ePO server? By default on a 32-bit machine this will be C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\DB\Agent_<computername>.log and for 64-bit systems C:\ProgramData\McAfee\Common Framework\DB\Agent_<computername>.log.

I can only assume that there hasn't been any changes to the DC that has the ePO installed e.g. IPv6 enabled, new network interface installed, host name change, network routes/firewalls etc. McAfee Agent attempts to connect to the ePO in the order of last known IP address, DNS name, or NetBIOS name, so in theory if you haven't changed the IP address of your ePO then endpoints should still be able to communicate.

You might also want to check that there is no conflicts with a possible new component installed on your existing DC and the ePO communication ports.

HTH,

Mick

View solution in original post

Highlighted

Re: Added a Secondary Domain Controller

Jump to solution

So, i rebooted the primary DC due to windows updates and everything started working....

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community