Nmap Development mailing list archives

Re: NMAP 7.31 & Npcap 0.10 R9 Error


From: 食肉大灰兔V5 <hsluoyz () gmail com>
Date: Thu, 3 Nov 2016 21:56:12 +0800

Hi Philip,

The new loopback adapter is for Nmap to scan the localhost. If you don't
need this feature, you can uncheck the "Support loopback traffic ("Npcap
Loopback Adapter" will be created)" option in the Npcap installation wizard.


Cheers,
Yang


On Thu, Nov 3, 2016 at 8:44 PM, Philip Kroetsch <pkroetsch () minnkota com>
wrote:

Is the new loopback network adapter that npcap creates required or can
that be disabled?



*From:* dev [mailto:dev-bounces () nmap org] *On Behalf Of *postal dude
*Sent:* Tuesday, November 01, 2016 2:10 PM
*To:* dev () nmap org

*Subject:* Re: NMAP 7.31 & Npcap 0.10 R9 Error



Check the output of nmap --iflist.

If your eth0 is not mapped to a WINDEVICE, try resetting your tcp/ip
stack with 'netsh int ip reset' and reboot. Then try again.

On 01.11.2016 19:25, Philip Kroetsch wrote:
Ok. The successfully installed npcap. Now when I run nmap I am getting
an error.

“dnet: Failed to pen device eht0”
QUITTING!

Thanks


From: dev [mailto:dev-bounces () nmap org <dev-bounces () nmap org>] On
Behalf Of ?????V5
Sent: Tuesday, November 01, 2016 11:31 AM
To: Nmap-dev <dev () nmap org>
Subject: Re: NMAP 7.31 & Npcap 0.10 R9 Error

Hi Philip,

The file said:
Error 0x800b010a: A certificate chain could not be built to a trusted
root authority.

From MSDN here: https://support.microsoft.com/en-hk/kb/2746268<https://
support.microsoft.com/en-hk/kb/2746268> (although it's for Win7 and not
Win8), it said this happens when your computer is not connected to
Internet, so Windows can't download the root trust cert remotely when
verifying the signature? Have your machine connected to Internet? If not,
you can follow this document (https://technet.microsoft.
com/en-hk/library/dn265983.aspx<https://technet.
microsoft.com/en-hk/library/dn265983.aspx>) to configure your trust root
manually.

A more direct (but a little unsafe way) to do this is to disable your
driver signature enforcement on your Win 2012 (if it's possible) based on
this docs: https://learn.sparkfun.com/tutorials/disabling-driver-
signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8<
https://learn.sparkfun.com/tutorials/disabling-driver-
signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8>.
But I don't know if you want to do this.


Cheers,
Yang


On Wed, Nov 2, 2016 at 12:03 AM, Philip Kroetsch <
pkroetsch () minnkota com<mailto:pkroetsch () minnkota com>> wrote:
I got the same error when installing r13.

From: dev [mailto:dev-bounces () nmap org<mailto:dev-bounces () nmap org>
<dev-bounces () nmap org%3cmailto:dev-bounces () nmap org%3e>] On Behalf Of
?????V5
Sent: Tuesday, November 01, 2016 10:50 AM

To: Nmap-dev <dev () nmap org<mailto:dev () nmap org>>
Subject: Re: NMAP 7.31 & Npcap 0.10 R9 Error

Hi Philip,

It seems to be a signature issue. The SetupCopyOEMInf() call fails with
0xe0000247. There's a similar issue in MSDN: http://answers.microsoft.com/
en-us/windows/forum/windows_8-winapps/error-0xe0000247-
problem-in-setupcopyoemlnfw-file/dfa77f92-f852-418b-bbca-
9a0417320f81?page=1<http://answers.microsoft.com/en-us/
windows/forum/windows_8-winapps/error-0xe0000247-
problem-in-setupcopyoemlnfw-file/dfa77f92-f852-418b-bbca-
9a0417320f81?page=1>. This issue only happens on Win8/Win2012. And you're
using Win2012.

You can send me your C:\Windows\INF\setupapi.dev.log to double-check
it. That file should indicates that the signature checking fails with
Npcap's driver.

I tried to fix it in a Npcap 0.10 r13 test build here:
https://github.com/nmap/npcap/releases/download/v0.10-r12/
npcap-0.10-r13-test.exe<https://github.com/nmap/npcap/
releases/download/v0.10-r12/npcap-0.10-r13-test.exe>

Please test it to see whether it solves your issue.


Cheers,
Yang






On Tue, Nov 1, 2016 at 9:48 PM, Philip Kroetsch <pkroetsch () minnkota com<
mailto:pkroetsch () minnkota com>> wrote:
Thanks
Phil

From: dev [mailto:dev-bounces () nmap org<mailto:dev-bounces () nmap org>
<dev-bounces () nmap org%3cmailto:dev-bounces () nmap org%3e>] On Behalf Of
?????V5
Sent: Tuesday, November 01, 2016 4:29 AM
To: Nmap-dev <dev () nmap org<mailto:dev () nmap org>>
Subject: Re: NMAP 7.31 & Npcap 0.10 R9 Error

Hi Philip,

Please provide the entire NPFInstall.log and DiagReport to me. I can't
tell what's actually wrong with the current info you provided. If you feel
it unfit to make them public, you can send me the files privately to my
mail. Thanks!


Cheers,
Yang


On Mon, Oct 31, 2016 at 10:00 PM, Philip Kroetsch <
pkroetsch () minnkota com<mailto:pkroetsch () minnkota com>> wrote:
Hello,

I am getting an error when installing NMAP 7.31. The first error is on
installation for npcap this is the error I receive “Failed to create npcap
service for Win7, Win8, and Win10. Please try installing Npcap again, or
use the official Npcap installer from https://github.com/nmap/releases<
https://github.com/nmap/releases>”

I then tried installing npcap-0.10-r12 and received the same error. This
has happened on 3 separate windows server 2012 instances and 2 windows 8.1
instances.

Then now when I go to run nmap this is the error I receive. “Warning:
Could not import all necessary Npcap functions. You may need to upgrade to
version 0.07 or higher”

I looked in the NPFInstall.log file and I looks like there was a few
errors. “HrInstallNetComponent” “Error 0xe0000247: Couldn’t install the
network component” “Error 0xe0000247: InstallSpecifiedComponent”

Any help is appreciated.

Thank you!

________________________________
This email has been scanned for email related threats and delivered
safely by Mimecast.
For more information please visit http://www.mimecast.com<http:/
/www.mimecast.com>
________________________________

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


________________________________
This email has been scanned for email related threats and delivered
safely by Mimecast.
For more information please visit http://www.mimecast.com<http:/
/www.mimecast.com>
________________________________


________________________________
This email has been scanned for email related threats and delivered
safely by Mimecast.
For more information please visit http://www.mimecast.com<http:/
/www.mimecast.com>
________________________________
------------------------------------------------------------
---------------------------
This email has been scanned for email related threats and delivered
safely by Mimecast.
For more information please visit http://www.mimecast.com
------------------------------------------------------------
---------------------------



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


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


------------------------------
This email has been scanned for email related threats and delivered safely
by Mimecast.
For more information please visit http://www.mimecast.com
------------------------------

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

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

Current thread: