1 Reply Latest reply on Apr 10, 2013 12:56 PM by mrspike

    LANDesk 9.0 SP3 and Symantec Endpoint Protection 12.1

    Rookie

      Something i recently found and wondering if anyone else had the same issue and a better resolution then me .

       

      Been seeing some weird issues with LANDesk Client and Symantec Endpoint Protection installed on a Windows 7 32bit PC

       

      when viewing the Syamantec Firewall logs i noticed that my ip address of the Client machine that has symantec installed is appearing in the remote Host Section and thus a server appearing in the Local Host of the logs

      which causes my Symantec logs to log everything as being blocked cause it is unable to match any rules to the traffic.

      This leaves me with the obviouse lack of confidance in the logs that i see and the firewall working as expected since even though the logs are saying blocked i see no lack of function on the PC

       

      Obviously call logged to Syamntec and they have not been able to find a resolution to the problem to date .

       

      A Colleague was having an simular issue with Wireshark

       

      after a bit of testing i was able get it down to the LANDESK XDD client causing the issue when i install LANDesk without the XDD and Symantec Endpoint protect everything works fine

       

      a slap on the wrist for me cause i did have every machine installed with XDD so i have a nice long task of pushing out a updated client without the XDD as from what i understand XDD is only used for finding unmanaged clients behind a firewall

       

       

      I guess just wondering if anyone else has had a simular issue

        • 1. Re: LANDesk 9.0 SP3 and Symantec Endpoint Protection 12.1
          mrspike SSMMVPGroup

          We have SEP 12.1.2015.2015 and LANDesk 9.0 SP3 installed and have not noticed any issues, we do not have an XDD agents.   As you found, you only want to install the XDD Agent on a few systems per subnet and NEVER on a laptop.... you do not want to discover outside systems.

           

          When we were using XDD we were sure to add -XDD in the name of the agent to make it clear it was enabled.