Endpoint Protection

 View Only
  • 1.  SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 09:43 AM

    hello,

    I need an answer.

    SEPM server is in different VLAN then clients.

    I have created a firewall rule where are only 2 rules:

    1 Allow all outgoing

    2 Block all

    These rules should block any incoming packets. It works but not from the subnet where is the SEPM server located. From this subnet, I can ping, telnet...everything.

    Is this a feature, or bug?

     

    Rudolf



  • 2.  RE: SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 09:46 AM

    What is the Traffic log showing?



  • 3.  RE: SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 09:52 AM

    I mean allow all .



  • 4.  RE: SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 09:52 AM

    It is a Feature of Firewall however check the ports and rules which says allow .



  • 5.  RE: SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 09:58 AM

    I don't see the traffic from the SEPM subnet. Only traffic other then SEPM subnet.

     

    strange



  • 6.  RE: SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 09:59 AM

    Allow all is only for outgoing traffic.

    Everything else should be blocked



  • 7.  RE: SEP FW does not match subnet where SEPM server is located

    Posted Apr 22, 2013 10:03 AM

    Follow the instruction here for enabling TSE debugging

    How to debug the Symantec Endpoint Protection client

    Article:TECH102412  |  Created: 2007-01-06  |  Updated: 2013-03-27  |  Article URL http://www.symantec.com/docs/TECH102412

     

    Should give us a better idea of what is going on



  • 8.  RE: SEP FW does not match subnet where SEPM server is located
    Best Answer

    Posted Apr 23, 2013 05:49 AM

    problem solved.

    I have exported the policy profile as xml. There was a unregulated_host_group in the HostGroupZones

    It was the IPS policy, where an subnet exclude was set

     

    Rudolf