Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Bug: Cannot find route to target
From: "Shreyas Zare" <shreyas () technitium com>
Date: Tue, 18 Dec 2007 23:09:11 +0530

Hi,

I am having a Win2003 machine configured as a router. The router uses
a Demand Dial interface to connect to the Internet. When I an starting
a scan with Nmap, it throws error:

===============================================================
Starting Nmap 4.50 ( http://insecure.org ) at 2007-12-17 20:47 India Standard Ti
me
WARNING: Unable to find appropriate interface for system route to 10.5.1.7

nexthost: failed to determine route to xxx.xxx.xxx.xxx
QUITTING!
===============================================================

The routing table has no issues and route print command gives following o/p

===============================================================
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
0x10003 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x10004 ...00 16 76 a3 9e 14 ...... Intel(R) 82566DC Gigabit Network Connection
0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
         0.0.0.0          0.0.0.0         10.5.1.7     10.5.231.166      1
        10.5.1.7  255.255.255.255     10.5.231.166     10.5.231.166      1
    10.5.231.166  255.255.255.255        127.0.0.1        127.0.0.1     50
  10.255.255.255  255.255.255.255     10.5.231.166     10.5.231.166     50
       127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
   192.168.100.0    255.255.255.0    192.168.100.1    192.168.100.1     20
   192.168.100.1  255.255.255.255        127.0.0.1        127.0.0.1     20
   192.168.100.4  255.255.255.255        127.0.0.1        127.0.0.1     50
 192.168.100.255  255.255.255.255    192.168.100.1    192.168.100.1     20
       224.0.0.0        240.0.0.0     10.5.231.166     10.5.231.166     50
       224.0.0.0        240.0.0.0    192.168.100.1    192.168.100.1     20
 255.255.255.255  255.255.255.255     10.5.231.166     10.5.231.166      1
 255.255.255.255  255.255.255.255    192.168.100.1    192.168.100.1      1
 255.255.255.255  255.255.255.255    192.168.100.4            10004      1
Default Gateway:          10.5.1.7
===========================================================================
Persistent Routes:
 None
===============================================================

Addidtional info is that the machine is behind a NAT of the ISP. All
other apps have no problems with the configuration. If I use a
standard Windows dialer to connect then there is no problem with Nmap.

Regards,

-- 
("Computers are useless. They can only give you answers." - Pablo Picasso)

Shreyas Zare
Co-Founder, Technitium
eMail: shreyas () technitium com

..::< The Technitium Team >::..
Visit us at www.technitium.com
Contact us at theteam () technitium com

Technitium Personal Computers
We believe in quality.
Visit http://pc.technitium.com for details.

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


  By Date           By Thread  

Current thread:
  • Bug: Cannot find route to target Shreyas Zare (Dec 18)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]