Endpoint Protection Small Business Edition

 View Only

  • 1.  EPMAP port blocked after new policy created

    Posted Mar 10, 2017 06:45 AM

    Hello guys,

    We have a SymantecCloud based SEP SBE. We have a Windows 8 VM and I wanted to back this pc up with Veeam.

    The backup is failing because Symantec firewall blocking the EPMAP port by default on the client.

    I've created a new Policy and enabled File and Print sharing firewall rule and created another rule to enable incoming traffic from Veeam's PC on port TCP 135.

    Unfortunatelly default EPMAP firewall rule rejecting the traffic. Do you have any idea if i missed something to set up?

    Please find attached screenshots.

     

    Thanks

    humat72

     



  • 2.  RE: EPMAP port blocked after new policy created

    Posted Mar 10, 2017 07:59 AM

    Did you move the rule to the top?



  • 3.  RE: EPMAP port blocked after new policy created

    Posted Mar 10, 2017 08:34 AM
      |   view attached

    Yes I did. Attached sreenshot.

    If the client doesn't connect to the symantec cloud server could that cause this issue?

    Thanks

     

     



  • 4.  RE: EPMAP port blocked after new policy created

    Posted Mar 10, 2017 08:37 AM

    Yes, it would to do this in order to get the policy update/change.



  • 5.  RE: EPMAP port blocked after new policy created

    Posted Mar 16, 2017 05:11 AM

    Thanks, it's sorted. Our main firewall blocked some traffic. Now is working perfectly