Trace failing on Directly connected Hosts

[GRANT3779]

I'm having an issue where if I run a traceroute from a router or switch to a host on a directly connected subnet - it's failing.. Just keep getting the * until 30 tries then stops.. I can ping the hosts no problem.. Only doing this for one site.. Any ideas??

[mfurnival]

Could it be that your router is using the wrong source inteface for the traceroute? Do an extended traceroute and specify the correct interface as the source.

[gordonderick]

It looks like there is a problem on the configuration either on the network or on the host. Can you do a 'show ip route x.x.x.x' where x.x.x.x is the ip address of your host and paste the o/p here.

[GRANT3779]

Hi Guys,

LH-HG-LH-01-01#show ip route 172.27.150.25

Routing entry for 172.27.150.0/24

  Known via "connected", distance 0, metric 0 (connected, via interface)

  Routing Descriptor Blocks:

  * directly connected, via FastEthernet0/0.1

      Route metric is 0, traffic share count is 1

Doesn't matter what address on the LAN I try to trace to, it doesn't work. I can ping no problem. Even an extended trace doesn't work...weird..

[gordonderick]

Thanks for that. Is it possible to provide o/p of FastEthernet0/0.1 config ?

[GRANT3779]

interface FastEthernet0/0.1

description Data

encapsulation dot1Q 1 native

ip address 172.27.150.1 255.255.255.0

ip nat inside

ip virtual-reassembly

end

[mfurnival]

Can you wireshark between the router and the host so we can see what is happening?

[GRANT3779]

It's a remote site, so not to sure on the options available to do that..