Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: A Problem with Nmap - All Ports are classified as open no matter what IP address I scan
From: Xander Solis <xrsolis () gmail com>
Date: Wed, 3 Jun 2009 18:14:47 +0800

Prof,

Maybe using nmap with tor and proxychains can help you on your scenario. On
the legalese on port scanning, a chapter in the nmap book has pointers on it

http://nmap.org/book/legal-issues.html#legal-crime

Hope this helps out.

On Wed, Jun 3, 2009 at 4:33 PM, Professor 0110 <professor0110 () gmail com>wrote:

Hi everyone,
I've been having this problem ever since I started using Nmap, but I
haven't
decided to ask for professional help until now.

Anyway, my problem is, whenever I scan an IP address with Nmap it
classifies
all ports as open, and ports 135, 139 and 445 as filtered. The only
exception to this case is when i scan my LAN . I am on a satellite
broadband
connection. However, whenever I use an alternate broadband connection, the
Nmap scan works as it should and only identifies ports that are open.

I ran a packet trace from the Nmap command line while scanning an IP
address
on the satellite broadband connection, and I received a SYN-ACK for all
ports Nmap scanned.

This is starting to get annoying, and I'm not sure how I can rectify this
problem.

Any help on this matter will be dearly appreciated!

Thank you,

Professor 0110

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




-- 
--
Xander Solis
xrsolis.blogspot.com

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


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]