Nmap Error Failed To Determine Dst Mac Address For Target
Packet crafters More Site News Advertising About/Contact Sponsors: Nmap Development mailing list archives By Date By Thread Failed to determine dst MAC address From: A Darren Dunham Date: Tue, 19 Jan 2010 08:41:55 +0000 I've looked through the archives, and I found a few older mentions of "Failed to determine dst MAC address", but it suggested that changes in the past should cause nmap to print a more helpful error message. I'm interested if this should still be happening. I'm running 5.00 (with pcap 4.0.2) on XP SP3. I am as you might expect trying to use this over VPN. "-iflist" shows all interfaces as type "ethernet" even the VPN. $ nmap -iflist Starting Nmap 5.00 ( http://nmap.org ) at 2010-01-19 00:23 Pacific Standard Time ************************INTERFACES************************ DEV (SHORT) IP/MASK TYPE UP MAC eth0 (eth0) 10.3.2.2/32 ethernet up 00:FF:B8:DA:4B:8A eth1 (eth1) 192.168.0.8/24 ethernet up 00:1F:3C:43:2F:66 eth2 (eth2) (null)/0 ethernet down 00:1C:23:4A:0F:74 lo0 (lo0) 127.0.0.1/8 loopback up DEV WINDEVICE eth0 \Device\NPF_{DFC7E06C-A91A-4C67-9E16-EC4466AEC12B} eth1 \Device\NPF_{76811572-32AD-4BAF-90A2-A52A042A9031} eth2 \Device\NPF_{1D03FB04-61AA-4E37-977A-6F0244134D0E} "eth0" is the VPN, eth1 is the machine's normal DSL connection. Another message I found suggested that this can be caused when the gateway used no longer exists. I've checked and every network that is behind the VPN shows the gateway of my local IP (the /32 above). Because the gateway is a /32 (and my local IP), I wonder if the problem is similar to the "scan 255.255.255.255" thread? (http://seclists.org/nmap-dev/2009/q4/203) I'm actually interested in just doing some very simple TCP port checks. If that's all that I need, is there a flag that would let nmap just do a normal TCP open without needing to determine MAC addresses? Thanks, and sorry if I missed something. -- Darren _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/ By Date By Thread Current thread: Failed to determine dst MAC address A Darren Dunham (Jan 19) Re: Failed to determine dst MAC address David Fifield (Jan 19) Re: Failed to
Packet crafters More Site News Advertising About/Contact Sponsors: Nmap Development mailing list archives By Date By Thread IPv6 Failed to determine dst MAC address for target From: Marcus Kipp Date: Wed, 2 Nov 2011 09:42:47 +0100 Hi, i have a question regarding the http://seclists.org/nmap-dev/2010/q1/173 following error message. nexthost: Failed to determine dst MAC address for target 2a00:ff::b0:b:12 [cid:image001.png@01CC9873.444E87C0] When I do some pings directly from host on cmd-line (Windows 7 Host) I can ping all IPv6 addresses. I also can make a ssh to this target. http://seclists.org/nmap-dev/2011/q4/213 But from NMAP I got this error ! Do you have an idea what happens here ? This is a windows 7 installation on a host. when I use a VM with win7 on that host with an usb network interface it works, but it hung up when I make a IPv6 scan incl. UDP. I´m using Zenmap 5.61 Test2. Regards Marcus _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/ By Date By Thread Current thread: IPv6 Failed to determine dst MAC address for target Marcus Kipp (Nov 02) Re: IPv6 Failed to determine dst MAC address for target David Fifield (Nov 02) [ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
NewsInternationalNew HiresRapid7 EventsRecruitingLeader PerspectivesDiscussionsAllAppSpiderMetasploitNexposeInsightIDRBlogsAllAppSpider Metasploit Nexpose InsightIDRInformation Security Rapid7 NewsLog inRegister0SearchSearchSearchCancelError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page.All Places > Nexpose > https://community.rapid7.com/thread/2167 DiscussionsLog in to create and rate content, and to follow, bookmark, and share content with other members.Not a member? Join Now!AnsweredAssumed AnsweredSite Scan Failures - Nmap: ERRORQuestion asked by borgy95 on Jul 24, 2012Latest reply on Jul 26, 2012 by ospannero Like • Show 0 Likes0 Comment • 3I have been running CCSVM fine, until recently when i had to do nmap error a reinstall when an infrastructure issue thrashed my machine. (love my storage guys ) anyhow so i have had to rebuild the machine. I have created exactly the same sites and tried scanning but i am being met with the following error. I am running it on a WIN2008R2 virtual machine.I have read in other posts this is related to Windows nmap error failed virtual WIFI Adaptor. I don't think this could be the issue as nothing has chnaged with the machines in my site.Below is the error:StatusFailed (java.io.IOException: The Nmap exit value is not zero (0). at com.rapid7.nexpose.scan.nmap.Nmap.start(Unknown Source) at com.rapid7.nexpose.scan.nmap.Nmap.run(Unknown Source) at com.rapid7.nexpose.scan.Scan.start(Unknown Source) at com.rapid7.nexpose.scan.Scan.run(Unknown Source) at java.lang.Thread.run(Unknown Source) )Looking at the log:NMAP: ERROR: nexthost: Failed to determine dst MAC address for targetThanks for the help.Jackborgy95 Jul 25, 2012 5:08 AMCorrect AnswerDefinitely no "Microsoft Virtual Wifi Miniport Adapter...this was the first thing i checked.But i ended up figuring out the issue:My VM had an additional nic. That I had used since building it and had forgotten to disconnect. It was configured to use dhcp. Once I disabled it and disconnected it through the vsphere client, there has not been any issues running a scan. I have in fact completed a scan successfully now.I figured it had to be something to do with the CCSVM server as I ran a test scan on a different vm and it failed again with the same error. See the reply in contextNo one else had this quest