got one for ya !!!!!! why can't in ping

aueddonline

ok

i've got two 2610 routers connected over a serial link, clocking set on the DCE side.

2610a serial 0/0 ip address 172.16.64.10 /19

2610b serial 0/0 ip address 172.16.64.1 /19

then i've got a 3500 switch connected to e0/0 on 2610b

and a TFTP server plugged into the switch

s3500 int VLAN 1 ip address 172.16.96.50

TFTP server 172.16.96.52

here's the weird bit

i can ping 2610a to 2610b s0/0
i can ping 2610a to 2610b e0/0
i can ping 2610b to s3500
i can ping 2610b to TFTP server
i can ping everything!!!!!!!! apart from.... 2610a to anything on the 96 network,

what is going on?

aueddonline

oh apart from e0/0 which is on the 96 network

Netstudent

Do you have a route to that subnet?

ip route 172.16.96.0 255.255.224.0 172.16.64.1

aueddonline

yeah 2610b has s0/0 on the 64 network and e0/0 on the 96 network

Netstudent

Can you post the running-configs for the routers?

Or do a traceroute and post the results.

you can also try an extended ping from routerA but give the echo request an IP from one of routerB's subnets. If the reply comes back then it probably isn't a routing problem.

wildfire

It hard to tell without looking at configs, but;

What has your TFTP server etc got as a default gateway? if the switch is the gateway do you have a static pointing to the serial network?

post some configs here

Netstudent

wildfire wrote:

It hard to tell without looking at configs, but;

What has your TFTP server etc got as a default gateway? if the switch is the gateway do you have a static pointing to the serial network?

post some configs here

Are all 3500 switches layer 3 or just the 3550?

aueddonline

give me half an hour i'll get you guys some configs

Slowhand

Does 2610a have a route to the 172.16.96.0/19 network? If you can't ping anything in that network from the first router, then I'd say you need to check the routing table on that device and make sure you have a route to the network you want. If you're directly connected, as you said, through e0/0, then you should check the ip address and netmask on that interface (and make sure it's up/up.) Can you ping any device on the 172.16.96.0/19 network from 2610b?

aueddonline

the switch inquestion is a 3524 layer 2 switch

Netstudent

Slowhand wrote:

Does 2610a have a route to the 172.16.96.0/19 network? If you can't ping anything in that network from the first router, then I'd say you need to check the routing table on that device and make sure you have a route to the network you want. If you're directly connected, as you said, through e0/0, then you should check the ip address and netmask on that interface (and make sure it's up/up.) Can you ping any device on the 172.16.96.0/19 network from 2610b?

Thats the same thing I asked in the 3rd post of this thread. That would be my first place to look as well. he says he does though, but we'll see when he posts the configs.

Netstudent

aueddonline wrote:

the switch inquestion is a 3524 layer 2 switch

Well then mkae sure you don;t have the default gateway set on that tftp server as the switch's vlan interface IP. As others just stated, double check your default gateways and subnets. Do you have a routing protocol or did you manualy configure the route to RouterB's Ethernet interface from routerA?

aueddonline

welldone guys I had the default gateway wrong on the switch!

why was i able to telnet from 2610a to 2610b and then from there to the switch when i was plug into the 2610a with a console cable.

Slowhand

aueddonline wrote:

welldone guys I had the default gateway wrong on the switch!

why was i able to telnet from 2610a to 2610b and then from there to the switch when i was plug into the 2610a with a console cable.

Probably because you're directly connected to the switch from 2610b. If you log into 2610a directly, then telnet to 2610b, you're on 2610b as far as the switch is concerned.

Netstudent

indeed