Nessus Client/Command Line differences

I was doing some testing with Nessus and found that one of the plugins only 
seems to run when using the Linux Nessus Client and not the command line.  To 
test this, I set up a policy in Nessus Client to scan using only plugin 11765, 
"scan for UPNP/Tcp hosts", and set it to enable dependencies at run time.  When 
I run the scan against the target host, that plugin appears to run and its 
result appears in the report.

Next I ran a command line scan using the nessusrc file from the Client 
configuration above to make sure all selections are exactly the same.  I run 
the following command:
/opt/nessus/bin/nessus -c nessusrc_upnp -T nbe -q localhost 1241 [user] 
[password] targets.txt output_upnp.nbe

The plugin does not appear to run at all, as its result doesn't show up in the 
output and nothing happens in the packet capture after the port scan.

Any idea why this would be happening, or has anything experienced this with 
other plugins?

-Will
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus