Re: Nmap and Sygate Personal Firewall

[kx <kxmail () gmail com>]

I posted about the same issues here:

http://seclists.org/lists/nmap-dev/2006/Apr-Jun/0068.html

I believe it is a Sygate or Winpcap issue, and not nmap specific.  The
reason I believe this is I had no problems with Sygate 5.1 or 5.5, and
when I upgraded to Sygate 5.6, everything got hosed. This included old
versions of nmap, I tested back to about version 3.5, and these
versions were all working fine prior to the firewall upgrade.

Also winpcap has been upgraded fairly recently (late 2005-ish) and
winpcap binaries ship with the new windows installer. It could be some
odd behavior going on with sygate/winpcap interaction.

Because SPF is no longer supported, and this seems to affect so few
users, I doubt anyone is going to try to get to the root of this, but
please give it a try if you'd like. However, if there is a deeper
winpcap issues that rears its head with other symptoms, it might be
worth poking at.

Otherwise, I recommend remembering to turn off the firewall prior to
using nmap, then turn it back on after.

Cheers,
  kx


On 5/22/06, Jim Hayes <sd1986 () optonline net> wrote:
> In the past I was able to perform scans with the Sygate PF enabled and
> had no issues.  Recently I am having issues with network connectivity
> after a scan and need to reboot.  If I disable the FW before the scan
> then I will not run into any problems.
>
> Anyone have any thoughts on how I can resolve
>
> Using the latest versions of Nmap and version 5.6 of the Sygate Personal
> Firewall
>
> Jim
>
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev