Security Basics mailing list archives
Re: Port Scanning with Languard and nmap question
From: Adam Jones <ajones1 () gmail com>
Date: Thu, 28 Oct 2004 13:20:45 -0500
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
Current thread:
- Port Scanning with Languard and nmap question Carl Wilson (Oct 28)
- Re: Port Scanning with Languard and nmap question Adam Jones (Oct 28)
- Re: Port Scanning with Languard and nmap question Bruno G. San Alejo (Oct 29)