I tried to increase the timeout from 15 (which worked for a long time) to 100 which said vulnerable, and then to 500 which came out as not vulnerable. What exactly does this timeout do? Will it cause false negatives in the reports?
Thanks, David Sayre Los Alamos National Labs On Wednesday 24 September 2003 10:11 am, Renaud Deraison wrote: > On Wed, Sep 24, 2003 at 09:58:52AM -0600, David Kyle Sayre wrote: > > I am all of a sudden getting false positives on a large number of my > > machines. These were scanning clean, and then on Monday morning started > > showing dirty, but I hadn't changed anything. The one thing I noticed was > > that if I switched subnets, I got different results. I am pretty sure it > > is a networking problem, but can't seem to track it down, and was > > wondering if someone has seen these symptoms before. Any ideas. These are > > the results I got running the modified nasl that was sent out version > > 1.11, and I am currently running 1.18, and tried 1.21 with the same > > results. > > Try to increase "checks_read_timeout" in your .nessusrc and run the > plugin from nessusd, and see if that helps. > > > -- Renaud
