Ticket #434 (new defect)

Opened 2 years ago

Last modified 2 years ago

Wrong port scanning report generated by nmap in UMIT

Reported by: dhritimanh Owned by: boltrix
Priority: high Milestone:
Component: Umit Version: current svn
Keywords: umit,nmap, Cc: luis.kop@…

Description

Hello Everyone,

I run the UMIT tool from my virtual xp machine (sp1, version=2002) to my virtual Bactrack machine (both are connected through virtual network), and run the scan for detection of OS. In the Backtrack OS, i had opened port 80 as i viewing web pages in the browser. But, in the nmap report of the UMIT tool in the virtual Xp, it stated that all ports of the 1000 ports that were scanned were closed. Now, Its wrong information as we can see.

I guess what we should do is we should in some way increase the port scanning capacity of the nmap and it shouldn't be limited to a random 1000 ports. It should be comprehensive enough to atleast scan the common ports such as 80.

Change History

Changed 2 years ago by angad

NMAP scans the most common ports of each protocol as mentioned here http://nmap.org/book/man-port-specification.html and I believe it does scan port 80. Have you tried manually specifying scanning port 80? There could be some issue with your virtual network.

Changed 2 years ago by luis

Which profile did you use?

Note: See TracTickets for help on using tickets.