Results 1 to 8 of 8
Configuration: Windows XP, NMAP 5.21
Target: Remote RHEL 5
I am connected to the remote box via Cisco VPN.
I can ping the remote box.
When I run NMAP, I ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-19-2010 #1Just Joined!
- Join Date
- Sep 2010
- Posts
- 40
NMAP Issue....
Configuration: Windows XP, NMAP 5.21
Target: Remote RHEL 5
I am connected to the remote box via Cisco VPN.
I can ping the remote box.
When I run NMAP, I get:
Starting Nmap 5.21 ( Nmap - Free Security Scanner For Network Exploration & Security Audits. ) at 2010-10-19 14:04 Eastern Daylight Time
NSE: Loaded 36 scripts for scanning.
nexthost: Failed to determine dst MAC address for target xxx.xxx.xxx.xxx
QUITTING!
(Obviously I have obscured the IP)
Oh, forgot to mention the remote box is actually a Virtual Machine (VMware ESX).
ideas?
Thanks,
Ray
- 10-20-2010 #2
- 10-20-2010 #3Just Joined!
- Join Date
- Sep 2010
- Posts
- 40
- 10-20-2010 #4
-p 1-65535
this is a wrong parameter, try it without a space between -p and 1-65535
the rest looks good
- 10-20-2010 #5
- 10-20-2010 #6
Do you run nmap on windows? Which kind of adapter are you using (PPP / dial-up or such)? Where is the destination machine located (same subnet, internet, ..)?
Got a old bug in mind that should no longer exist in nmap since version 3.96, but who knows.
From nmap changelog:
Fixed a problem which led to the error message "Failed to determine
dst MAC address for target" when you try to run Nmap using a
dialup/PPP adapter on Windows rather than a real ethernet card. Due
to Microsoft breaking raw sockets, Nmap no longer supports dialup
adapters, but it should now give you a clearer error message than
the "dst MAC address" nonsense.Last edited by Kloschüssel; 10-20-2010 at 07:05 PM.
- 10-20-2010 #7Just Joined!
- Join Date
- Sep 2010
- Posts
- 40
- 10-20-2010 #8
That won't work for nmap. It uses some libraries where dialup, vpn and such type of interfaces are broken since WinXP SP2 because there the raw sockets are hidden and thus inaccessible to nmap. Give a live CD of your favorite linux distribution a try.

Please file a bug to the nmap dev mailing list / issue tracker as the error message should definitely be more verbose on the type of error since nmap 3.96.


Reply With Quote

