Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Fail error of nmap on Win Vista
From: Michael Pattrick <mpattrick () rhinovirus org>
Date: Wed, 1 Jul 2009 00:18:37 -0400

On Tue, Jun 30, 2009 at 12:40 AM, Santiago
Monterrosa<israel.64 () gmail com> wrote:
Starting Nmap 4.90RC1 ( http://nmap.org ) at 2009-06-29 23:17 Central
Daylight Time (Mexico)

NSE: Loaded 0 scripts for scanning.

Initiating Ping Scan at 23:17

dnet: Failed to open device eth4

QUITTING!
After following command: nmap -O -v 201.149.5.34

On Tue, Jun 30, 2009 at 8:04 PM, Santiago Monterrosa<israel.64 () gmail com> wrote:
eth4  (eth4)  (null)/0      ethernet    down 00:A0:D1:81:A3:87
eth14 (eth14) 20.1.31.61/24 ethernet    up   00:16:44:15:20:37

I'm assuming that the output from the original scan was not modified?
It appears as though nmap is using eth4 for some reason even though
eth14 is the one with an IP. You could use the command "nmap.exe -e
eth14 targethost" to force nmap to use the correct interface. However,
that doesn't seem to be the only issue.


On Tue, Jun 30, 2009 at 8:04 PM, Santiago Monterrosa<israel.64 () gmail com> wrote:
DEV   WINDEVICE
eth4  <none>
eth14 <none>

eth14 should have a WINDEVICE. If you are running cmd.exe as
administrator then Nmap should be able to retrieve this information,
it may be some 3rd party software blocking nmap in this case... or
something that I haven't thought of ;)

Cheers,
Michael Pattrick

_______________________________________________
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 ]