Hi TCP-IP gurus,
I have a local ethernet device configured with the IP address 10.3.0.1 and a netmask of 255.255.0.0 .
When I try to ping the device, the ICMP echo messages get routed to the local loopback interface instead
of the ethernet device itself. Is there a way to force the local routing table to allow the packets destined
for 10.3.0.1 to actually reach that IP address instead of the 127.0.0.1 loopback interface ???
Here is the routing table configuration.
0x4 ...00 ff f6 7a a8 30 ...... TAP-Win32 Adapter V8 - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask
10.3.0.1 255.255.255.255
Gateway Interface Metric
127.0.0.1 127.0.0.1 1
Persistent Routes:
None
I have a local ethernet device configured with the IP address 10.3.0.1 and a netmask of 255.255.0.0 .
When I try to ping the device, the ICMP echo messages get routed to the local loopback interface instead
of the ethernet device itself. Is there a way to force the local routing table to allow the packets destined
for 10.3.0.1 to actually reach that IP address instead of the 127.0.0.1 loopback interface ???
Here is the routing table configuration.
0x4 ...00 ff f6 7a a8 30 ...... TAP-Win32 Adapter V8 - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask
10.3.0.1 255.255.255.255
Gateway Interface Metric
127.0.0.1 127.0.0.1 1
Persistent Routes:
None