>You may want to try to switch to the SYN scanner instead of the tcp
>connect() one which is very slow against firewalled hosts.
 
In the past I had been using nmap, ping, as well as the tcp connect(), before I started the scan last night I turned off nmap, ping, and tcp connect.  I then turned on SYN scan and let it run.  In addition, I left out the network printers that were on that subnet and turned the maximum hosts scanned down to 10.  When I left last night it appeared that the scan had already stopped although only a third of the scan was complete.  I came in this morning and the scan was still at the same spot that it was when I left. 
 
>You may want to do a "ps auxw" on the nessusd side to see which processes are still >there
 
I did a "ps auxw" and the line referencing nessusd is as follows:
 
root     1789   0.0   0.9   4888  2536  ?        S    07:29   0:00 nessusd: waiting
for incoming connections
 
Do you have any other suggestions?  Thanks again for all your help!

Steve
 
p.s.  As I stated in an earlier message, I have recently upgraded my PC.  Other than the hardware changes, there was one major software change, the addition of Cisco Security Agent.  Is there a possibility that Cisco Security Agent is interfering with the connection between the client and the host?  Again, I have successfully scanned subnets on this new PC, but all of the ones I have been successful with were little used subnets that scanned quickly.


Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to