1st update: OK (Win7; NS: 20161004.002) (W10; NSBU: v20160223.011) 2nd one: (NS on W7: performed a reboot.
IPS, v20161004.002) (NSBU on W7: v20160223.011) 3rd upgrade: (NS, v188.8.131.52, on W7: Performed a reboot.
Got this line: IPS, v20161004.002) 4th for NSBU - it took longer to get the latest update S.
Small changes in computer settings or a change in configuration with router or modem settings may result in DNS error.
The next step was to open these website with browsers such as IE, Firefox and Chrome.
The logic is to check if it as a browser related problem.
Now the last two weeks Norton with all its problems, It also has started giving problems with the updating of the definitions, more precisely with the definitions of ''norton ips definition'' and rare occasions with ''reputation revocation list'' ... As we don't know when an update is available at Norton's end, how to we know when to set the logger in action and run it 3/4 hours at a time, as we are not aware when the IPS is due an update, this means leaving logger on continuously? Perhaps Norton should do this themselves, there have issued 184.108.40.206 with a bug in it, what happened to pre issue testing? The first time the IPS updated, it failed, but succeeded about a minute later. This is the first time in quite a while that IPS failed for me. I did the following TESTS on a Windows 10 & a Windows 7 computer: BTW, I have a question: What does Detected mean when it comes to Intrusion Prevention - Status?
I am very tired of Norton, This antivirus has a lot of problems! @Sunil_GA I had IPS Defs fail on manual LU on both NS Premium (WIN 10 AV) and Comcast's Norton Security Suite (Win 7). I have noticed this sequence over the last few days - possibly ever since 220.127.116.11.