Router not reaching specific IP address

[projectit]

Hello:

I'm trying to reach an specific IP address within my own LAN and I'm not able to ping. If I tracert I only get to the router of the site. The router is running RIP and EIGRP. Any help. Thanks

[Kevin Dorrell]

Where are you pinging from - from a PC on the LAN itself?

It sounds like the router has a more-specific route, or even a host route, to that destination, and is doing proxy ARP. Log in to the router and do a show ip route a.b.c.d for the target address, and see what it comes up with.

Could you be more specific about the addresses? Maybe that would help us spot something.

Kevin Dorrell

Luxembourg

[Richard Burts]

In addition to Kevin's suggestion I think it would be helpful to do show arp on the router and see if there is an ARP entry for the target IP address.

I am also a bit confused about the question. In the beginning of the question you say that you are trying to reach an address in your own LAN. I would interpret this as meaning that you are locally connected to the destination. Then you talk about traceroute getting to the router where the address is. Perhaps you could clarify a bit about the topology of the network.

HTH

Rick

[projectit]

Hello:

Ok from the site I'm able to reach the ip since I'm in the same subnet. The issue is that I want to be able to reach that IP address from another subnet within my own lan. The problem I'm getting is that if I tracert from another location I could only get to the router located at that site. Any help. Thanks

[Richard Burts]

If I understand correctly you can access the device at that address from devices within the same subnet. But can not access the device from devices in remote subnets.

There are a couple of things that could lead to those symptoms:

- it might be a problem with the configuration of default gateway on the target PC. you can access from local attached devices because you do not need default gateway for local addresses. But you do need the default gateway for remote addresses. Please check the PC and verify that its default gateway definition points to the IP address of the router interface.

- it might be a problem that the remote device does not have a route to the destination subnet. Can you verify that the routing table on the remote does have a route that correctly points to the destination subnet.

- it might be a problem that the local router does not have a route back to the remote source. Can you verify that the routing table on the router where the destination is connected does have a route back to the remote device.

If this does not clear it up then perhaps you can give us some more information about the topology of the network.

HTH

Rick

[projectit]

Kevin:

Attach is a sh ip route 130.108.101.12. I want to be able to reach this IP from another location. Any help. Thanks

[Richard Burts]

The show ip route indicates that the address is directly connected on interface FastEthernet0/0. Is that where you believe the device is connected?

Where is the device that you are using when you attempt this access?

The show ip route indicates that the entire class B 130.108.0.0 is on FastEthernet0/0 and is not subnetted. Is that correct?

HTH

Rick

[projectit]

Rick:

Within the subnet I'm able to get to the IP. Is when I'm at another subnet like 130.107.0.0/16 that I could only reach the router 130.108.100.1 and cannot get pass there. I don't have no Idea what else to do here. Thanks

[Richard Burts]

It would help to have a few specifics.

- Is the address of the PC 130.108.101.12? And is it connected to FastEthernet0/0 ?

- Where are you coming from when you have a problem? (what address, what subnet, is it another subnet on the same router or is it connected on another router)?

As I said in another post I think that you should check the PC and verify how its default gateway is configured.

It would probably be helpful if you would post the output of show ip route on the router where the PC is connected.

HTH

Rick

[ankurbhasin]

Hi Projectit,

Not very clear with your network scenario. Does yourself and the specific ip address you waan a reach are in different or same subnet. If you are in same subnet trace should not have taken you to the router.

If you are in different subnet you will reach the router first and router will throw you to that subnet so check if your routing table has that specidif subnet in table.

If this is no the scene please explain your network topology and paste your routing table.

Ankur

[projectit]

Here's the scenario. I have a network with class b subnet and within that LAN I have a class c subnet which I want to access from that class b subnet. The Network consists of two 2620 routers and 2950 switches. I'm not able to ping the class c subnet from outside the network, example ( corporate class b subnet to access this ip remotely.

[Richard Burts]

This is not enough specifics to clarify the problem. Partly you talk here about a class B and a class C. But your previous posts have talked about 130.107.0.0 and 130.108.0.0 which are both class Bs.

I repeat the questions that I asked in a previous post:

It would help to have a few specifics.

- Is the address of the PC 130.108.101.12? And is it connected to FastEthernet0/0 ?

- Where are you coming from when you have a problem? (what address, what subnet, is it another subnet on the same router or is it connected on another router)?

As I said in another post I think that you should check the PC and verify how its default gateway is configured.

It would probably be helpful if you would post the output of show ip route on the router where the PC is connected.

If you provide this information we will be in a better position to help solve your problem.

HTH

Rick

[projectit]

I want to be able to reach IP 130.108.101.12 from the subnet 130.107.0.0. I'm not able to ping this IP from the 130.107.0.0 subnet. When I do a tracert I could only get to the router serial interface. 130.108.0.0. Like I post before there are 2 cisco 2620s.

Thanks

George

[Richard Burts]

George

Until you provide answers to the questions I have asked there is little we can do to help solve your problem.

HTH

Rick

[projectit]

The IP address 130.108.101.12 is not directly connected to fa0/0. This ip address is connected at another location within the lan which is connected by a 2950 switch. fa0/0 is connected to the same switch. The ip 130.108.101.12 is not a router but a pc. The router is on the 130.108.0.0 subnet. I'm at the subnet 130.107.0.0 and want to reach 130.108.101.12. Thats where I get the error.

Thanks

George.