I still have not installed that Windows 7 July Security Only Update on any of my laptops and it’s still DEFOCN 2 at AW for the Aug 2019 problem patches and really Symantic had to have Known that MS was switching to SHA-2 only as that’s been stated for a good long time by MS/Others. So I’ll wait for the hotfix and that come via Norton Security Suite’s updating functionality instead of having to sign-in and have to download and install that whole mess all over again. “We are planning to deliver hotfix releases based off of 14.2 RU1 MP1, 14.2 RU1, and 14.2 MP1.” “Will “X” version of SEP receive a hotfix?” More restrictive rules may work as well.In their Question/Answer section at that Syamntec link provided:
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. Symantec identifies this sped up traffic as port attacks in some cases. Lansweeper 6.0 scans the same network device ports as previous Lansweeper releases, but does so more quickly to speed up scanning. This may result in traffic being blocked and errors similar to the one below in your Symantec installation. 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.
0 kommentar(er)
