RE: Nmap has stopped working - Windows 8.1

["James M. Scardelis, CISA, CIPP, CIPP/IT, MCT, MCSE, CTT+" <jim () jceltd com>]

I had these issues as well on my Surface Pro 3 128GB for about a week and a half, and then they magically fixed 
themselves. I'm wondering if I have a later driver than other folks with the problem.

If those having the problem would like to send me a .txt file with the  output of the "systeminfo /FO CSV" command (run 
from an admin cmd prompt), I will be happy to compare with my results.

Sent from my Windows Phone
________________________________
From: Daniel Miller<mailto:bonsaiviking () gmail com>
Sent: ‎10/‎24/‎2014 8:54 AM
To: Nmap-dev<mailto:dev () nmap org>
Subject: Fwd: Nmap has stopped working - Windows 8.1

Forwarding Elrich's reply to the development list in case anyone can
help out. A couple observations:

1. It crashes on --iflist, which really narrows down the places it
could crash. Specifically, it crashes after it prints interfaces but
before it prints routes.

2. He has a point2point interface (historically problematic for Nmap
on Windows) that has only an IPv6 address (no IPv4 assigned).

3. The OUI for his eth1 and eth2 interfaces (32-59-B7) does not show
up in the IEEE MA-L/OUI list. It is a locally-administered address, 1
bit off from one of Microsoft's OUIs, 30-59-B7

Dan

---------- Forwarded message ----------
From: Elrich De Villiers <tillter123 () live com>
Date: Fri, Oct 24, 2014 at 8:51 AM
Subject: Re: Nmap has stopped working - Windows 8.1
To: Daniel Miller <bonsaiviking () gmail com>


Thanks for getting back to me!

I am trying to run this on a surface pro 3, 128gb version
It runs windows 8.1 pro
Has an Intel I5-4300u 1.90GHz processor

Here is what I get from the nmap --iflist:

Starting Nmap 6.47 ( http://nmap.org ) at 2014-10-24 09:51 Eastern Daylight Time

************************INTERFACES************************

DEV  (SHORT) IP/MASK                                TYPE        UP   MTU  MAC

eth0 (eth0)  fe80::REDACTED/64           ethernet    down 1500 60:02:92:REDACTED

eth0 (eth0)  169.254.REDACTED/4                       ethernet    down
1500 60:02:92:REDACTED

eth1 (eth1)  fe80::REDACTED/64           ethernet    down 1500 32:59:B7:REDACTED

eth1 (eth1)  169.254.REDACTED/4                      ethernet    down
1500 32:59:B7:REDACTED

eth2 (eth2)  fe80::REDACTED/64           ethernet    up   1500 30:59:B7:REDACTED

eth2 (eth2)  10.REDACTED/20                         ethernet    up
1500 30:59:B7:REDACTED

lo0  (lo0)   ::1/128                                loopback    up   -1

lo0  (lo0)   127.0.0.1/8                            loopback    up   -1

tun0 (tun0)  2001:0:REDACTED/0 point2point up   1280

tun0 (tun0)  fe80::REDACTED/0            point2point up   1280

tun1 (tun1)  fe80::REDACTED/128                point2point down 1280

That is all I get but this command also results in the nmap has
stopped working error

I tried all the other commands you suggested and they all also crash
nmap with the only output in the Nmap output tab being :

Starting Nmap 6.47 ( http://nmap.org ) at 2014-10-24 09:56 Eastern Daylight Time

I hope this helps you!

Elrich

Sent from Surface

From: Daniel Miller
Sent: ‎Thursday‎, ‎October‎ ‎23‎, ‎2014 ‎11‎:‎30‎ ‎PM
To: Elrich De Villiers
Cc: dev () nmap org

On Wed, Oct 22, 2014 at 1:22 PM, Elrich De Villiers <tillter123 () live com> wrote:
> Hey, today I tried to install Nmap with Zenmap on my surface pro 3 running
> windows 8.1, but every time I try to scan an IP I get the message Nmap has
> stopped working and the scan fails. Any ideas on what I could do to fix this
> would be greatly appreciated.
> Thanks!


Elrich,

Thank you for your bug report. Support for Windows users is important
to the Nmap project, and we have received several reports of crashes
on Windows 8.1. Unfortunately, I have not yet been able to reproduce
this crash. Please provide more information about your system so we
can diagnose and fix this problem:

1. output of nmap --iflist

2. Which of these (or all) commands crashes Nmap?
a. nmap -sn scanme.nmap.org
b. nmap -Pn scanme.nmap.org
c. nmap -sn 192.168.1.1 (or some other local-LAN address)
d. nmap -Pn 192.168.1.1

3. Is there anything else unusual about your Nmap install? Are you
using the executable installer or the zipfile? Are you running with
any special privileges or restrictions?

4. Is there anything special about your Windows installation that we
should know? What edition (RT, Home, Pro, Enterprise)? Any security
software (antivirus, firewall, etc.)? Specialized hardware?

Thank you so much for your feedback. With your help, we hope to have
this problem solved quickly.

Dan
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/