Nmap Development mailing list archives
nexthost: failed to determine route to x.x.x.x (Windows XP)
From: Kyle Brotheridge <kyle () connecttel com au>
Date: Sun, 2 Aug 2009 19:15:45 +1000
I realize this was a know issue in BSD (I've looked through the bug logs) - But this is when using windows. Version: v5.0 Windows installer used Environment: OS: Windows XP Professional SP3 in a virtual environment (VMWare ESXi host) NIC 1: VMware Accelerated AMD PCNet Adapter NIC 2: VMware Accelerated AMD PCNet Adapter NIC 2 is disabled in Network Connections NIC 1 is enabled with a DHCP supplied address: IP Address. . . . . . . . . . . . : 192.168.127.10 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.126.1 Example output: U:\>nmap -vvv -sS -p 1443 203.45.x.y Starting Nmap 5.00 ( http://nmap.org ) at 2009-07-24 10:59 AUS Eastern Standard Time NSE: Loaded 0 scripts for scanning. WARNING: Unable to find appropriate interface for system route to 192.168.126.1 nexthost: failed to determine route to 203.45.x.y QUITTING! Ideas? Regards, Kyle Brotheridge, _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- nexthost: failed to determine route to x.x.x.x (Windows XP) Kyle Brotheridge (Aug 04)