NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Surffa
Jul 08, 2019Apprentice
Vulnerability scan triggers HP printer to print pages
Hi all. It appears that the Armor vulnerability scan always causes my HP Laser printer to print three pages, containing a client version or similar. E.g. curl and version number or so. I'm quite s...
- Jun 18, 2020Now I have been running 2.5.1.16 for quite some time and so far not a single page has been printed out.
So perhaps this update finally fixed the issue.
Finally. Thanks.
Surffa
Mar 27, 2020Apprentice
I think you are now mixing devices?
From what I searched before, your dates might fit 40 series(?), but not the 20 that was linked above and at least I was now talking about.
That KB support document regarding .30 is also fairly recently dated, so it shouldn't be too old. And I can guarantee that it hasn't been available for my devices before this week..
From what I searched before, your dates might fit 40 series(?), but not the 20 that was linked above and at least I was now talking about.
That KB support document regarding .30 is also fairly recently dated, so it shouldn't be too old. And I can guarantee that it hasn't been available for my devices before this week..
Adrian97c
Mar 28, 2020Apprentice
Doing a manual downgrade from .36 to .30 on my RBR20, let’s see how this works.
- Adrian97cMar 31, 2020ApprenticeDowngrading to .30 from .36 did NOT fix the printing issue.
- SurffaApr 05, 2020Apprentice
Adrian97c that's curious, as my RBR20 has now been running .30 SW for 1,5 weeks now.
Assuming the old schedule, it should've been printing twice, which it hasn't.
Printer still seems to work, so I have sort of a feeling that for my HP, which I originally reported the problem with, is now somehow in order with the Armor.
- SurffaApr 11, 2020Apprentice
All right. So now after quite some time the printer printed out the garbage pages again. So I now switched the printer off again and let's see about the next FW update again.
So definitely this is still not fixed.
Why the behavior is not consistent every week is strange, did the vulnerability scan interval change, or is the Armor behavior simply no longer consistent.