5 Replies Latest reply on Apr 20, 2012 5:37 AM by JoeBidgood

    Epo is scanning network on port 135

    bostjanc

      Greetings!

       

      Another system admin in our company just confirmed that he receives reports on Epo scanning on port 135 every couple of minutes.

      I was wonder what would that be? The strangest thing is that this "scanning process" scans subnets which do not exist in our environment, for example: 192.168.sth.5

       

      If I take a look on Epolicy-console I see that we have set up only default ports:

      Agent-to-server communication port: 80
      Agent-to-server communication secure port: Enabled on port 443
      Agent wake-up communication port: 8081
      Agent broadcast communication port: 8082
      Console-to-application server communication port: 8443
      Client-to-server authenticated communication port: 8444


      We are using:

      4.6.0 epo

      Mcafee agent: 4.6.0.1694

      VirusScan 8.8.0.777

       

      Message was edited by: bostjanc on 4/20/12 8:33:55 AM GMT+01:00