Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 8
Report Inappropriate Content
Message 11 of 11

Re: Clients not switching back to ePO from Agent Handler in DMZ

Jump to solution

I've been able to work around this by the following:

  1. Change the split tunnel to force traffic to the external IP of the agent handler through the VPN tunnel.
  2. Create a Windows Firewall rule on the agent handler blocking TCP 80 and 443 from VPN and internal network subnets.

This essentially allows clients to connect to the agent handler when not on VPN or internal network, but blocks access to the agent handler once they connect to VPN or an internal network (be sure not to include the subnet your ePO server is on as it still needs to be able to communicate with the agent handler).

I've noticed that the agent will continue to try to connect to the agent handler and not immediately switch to the ePO server.  It seems to take two ASCI before it will switch over.  So, up to two hours with the default ASCI.  We're a small company (under 600 clients) so I may lower the ASCI to 30 min to force the change quicker.

While not ideal, this is working well enough.


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