An easy way to prevent errors like the one below and to allow for a successful network scan is to whitelist all traffic coming from your Lansweeper server. I also recommend that you verify that the headers and devels are the same version as the kernel. Symantec identifies this sped up traffic as port attacks in some cases. If your servers have a UEFI boot system, check that Secure Boot is disabled (after restarting the server you must wait several minutes for the change to be reflected in the SEPM console). Lansweeper 6.0 scans the same network device ports as previous Lansweeper releases, but does so more quickly to speed up scanning. Start SEP 14 Linux client using below commands in the given order. rootkerneltalks tmp /etc/init.d/symcfgd stop. Stop SEP 14 Linux client using single command below. This may result in traffic being blocked and errors similar to the one below in your Symantec installation. How to restart SEP 14 Linux client processes. Since the release of Lansweeper 6.0, Symantec Endpoint Protection in particular is prone to wrongly identifying Lansweeper traffic as port attacks on your devices. It is important to allow traffic from your Lansweeper server to these ports, to ensure a successful network scan. A list of scanned ports can be found in this knowledge base article. To pull data from the Linux, Unix, Mac and Windows computers, VMware servers and other devices in your network, Lansweeper queries a number of ports on the devices.

Symantec endpoint protection 14 linux