Erik Stephens wrote: > I don't know what "built-in" port(s) are used for the TCP ping. I'll > update the nessuskb if someone gives me the definitve answer to that. > My guess is port 80 only. I know it won't use all the ports in the > services file for the TCP ping phase. Technically, only a single > non-filtered port should be needed just to see if there is a host - > the host doesn't have to actually be listening on that port. What > ports are unfiltered on that host? That might explain why nessus > thinks the host is not alive. Try setting the "TCP ping destination > port" to 443 and see if nessus thinks the host is alive.
No - it scans for over 49 different ports - it's just that 443 isn't one of them. Yes, if I change the TCP port options to explicitly list 443 - it will find it - I'm just saying I think port 443 should be one of the "default" ports. -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
