Does nmap without the '-f' switch still detect the port as open? It's
probably a silly question, but you never know...


Yes without the -f option nmap finds the open port and it does find it with -F option, too.


Another possible issue is that you are running ping_host.nasl
(implicitly because it's a dependency of nmap.nasl) and using the
built-in port range, which does not include 1723. Try listing 1723
explicitly for "Ping the remote host[entry]:TCP ping destination port(s)"


I did and you're right. I set

Ping the remote host[entry]:TCP ping destination port(s) : = 1723

and now it finds the host up. Is it possible to set this to

Ping the remote host[entry]:TCP ping destination port(s) : = built-in, 1723

Well ok, this means that the nmap.nasl wrapper is not behaving the way nmap does, right? Or is nmap doing a TCP ping on its default ports and this functionality is outsourced to ping_the_remote_host in Nessus? Still, then 1723 should probably be added to the built-in ports, right? Would be nice if nmap and nmap.nasl would act the same, especially for analysis. I don't know, just my 2 cents...

Anyway, thanx very much for your help. Great I know how to get it running, now. Learning more every day....

Greetz
Chris

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to