RE: nmap wont' run on server 16

["Rob Nicholls" <robert () robnicholls co uk>]

Hi Russell,

 

I assume you've installed Server 2016 Standard with the Desktop Experience?
And presumably the install didn't report any issues during installation?
I've installed Server 2016 Standard as a Hyper-V VM and just downloaded and
installed Nmap 7.40 using all the default settings and there were no errors
during installation and everything looks okay (I can scan a physical host on
the same subnet and it returns accurate results).

 

Does Nmap crash before it displays anything at the command line? I believe
it checks whether the Npcap and NPF services are running before you might
see anything, so this could be related to checks for those components. Did
you install Npcap or are you using WinPcap? If you're using Npcap, did you
install it with the default Npcap installation settings?

 

Do you have AV software installed? Or any other third party software that
might interfere with applications? Are you running Nmap installed into a
local folder or running it from a network share?

 

Server 2016 is essentially the same code as Windows 10, so I'm a little bit
surprised it's failing on Server 2016 when Nmap 7.40 works fine on Windows
10, plus it seems to work fine for on my Server 2016 VM.

 

I notice that the error message below says "Faulting module name: ntdll.dll,
version: 6.3.9600.18233, time stamp: 0x56bb4e1d" - Version 6.3.9600
corresponds with Server 2012 R2. I'm not sure why you can see that version
number if you're actually running Server 2016. On my freshly installed VM
(i.e. without any patches) ntdll.dll reports a version number of
10.0.14393.447. I would expect to see it report 10.0.x if you're running in
Server 2016. Nmap also runs fine on my 2012 R2 hosts using a default
install.

 

This might be an issue with the configuration of your particular VM, rather
than anything wrong with Nmap itself?

 

Cheers,

 

Rob

 

 

From: dev [mailto:dev-bounces () nmap org] On Behalf Of Darnell, Russell
Matthew (System Operations)
Sent: 16 March 2017 20:43
To: dev () nmap org
Subject: nmap wont' run on server 16

 

Hey guys,

Long time user of Nmap.  I've got a fresh build of Server 2016 (standard) on
a VMware backend.  I get some funky errors when installing.  This server
only has one disk.  I grabbed a fresh copy of the latest stable 7.40
download.  I was trying to run it from the command window

 

Any pro tips?

 

Russell

 

 

Faulting application name: nmap.exe, version: 7.0.40.0, time stamp:
0x5858be4f

Faulting module name: ntdll.dll, version: 6.3.9600.18233, time stamp:
0x56bb4e1d

Exception code: 0xc000007b

Fault offset: 0x0009d3c2

Faulting process id: 0x3d0c

Faulting application start time: 0x01d29e933385c275

Faulting application path: C:\Program Files (x86)\Nmap\nmap.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 72637663-0a86-11e7-80ef-005056886b81

Faulting package full name: 

Faulting package-relative application ID: 

 

 

Windows cannot access the file  for one of the following reasons: there is a
problem with the network connection, the disk that the file is stored on, or
the storage drivers installed on this computer; or the disk is missing.
Windows closed the program Nmap because of this error.

 

Program: Nmap

File: 

 

The error value is listed in the Additional Data section.

User Action

1. Open the file again. This situation might be a temporary problem that
corrects itself when the program runs again.

2. If the file still cannot be accessed and

                - It is on the network, your network administrator should
verify that there is not a problem with the network and that the server can
be contacted.

                - It is on a removable disk, for example, a floppy disk or
CD-ROM, verify that the disk is fully inserted into the computer.

3. Check and repair the file system by running CHKDSK. To run CHKDSK, click
Start, click Run, type CMD, and then click OK. At the command prompt, type
CHKDSK /F, and then press ENTER.

4. If the problem persists, restore the file from a backup copy.

5. Determine whether other files on the same disk can be opened. If not, the
disk might be damaged. If it is a hard disk, contact your administrator or
computer hardware vendor for further assistance.

 

Additional Data

Error value: 00000000

Disk type: 0

 

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