Re: Port Scanning with Languard and nmap question
From: Adam Jones (ajones1_at_gmail.com)
Date: 10/28/04
- Previous message: Dan Barr: "Re: Securing Redhat Apache 2.0"
- In reply to: Carl Wilson: "Port Scanning with Languard and nmap question"
- Next in thread: Bruno G. San Alejo: "Re: Port Scanning with Languard and nmap question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 28 Oct 2004 13:20:45 -0500 To: Carl Wilson <chwilson0607@yahoo.com>
Latency would do it. It could be that languard is not waiting long
enough for returns from those ports, and is counting them as
filtered/closed. Look into your settings for languard and see if
increasing timeout values will help. Also try running the scan at a
slower speed. If the device is already doing something else when you
try to scan it you may not get a response in time while it processes
everything that came in before your connection request.
-Adam
- Previous message: Dan Barr: "Re: Securing Redhat Apache 2.0"
- In reply to: Carl Wilson: "Port Scanning with Languard and nmap question"
- Next in thread: Bruno G. San Alejo: "Re: Port Scanning with Languard and nmap question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|