Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to ping tftp server from neighbor router 2

Status
Not open for further replies.

hung0970

Programmer
Aug 12, 2010
1
0
0
US
I have 2 routers connected together via Serial port. One end of the eth0 Router1 connected to home-router (192.168.1.1). from Router 1, I am able to ping 192.168.1.1. One end of eth0 Router2 connected to TFTP server (10.1.1.1). From Router2, I am able to ping 10.1.1.1. From Router 1, I am also able to ping eth0 of Router2 (10.1.1.102) but not able to ping 10.1.1.1 vice versa from Router2, I am able to ping eth0 of Router1 (192.168.1.60) but not able to ping 192.168.1.1. Both Routers are 2511. Any help would be greatly appreciated. Please see below ping & configuration info. Thanks.
Hung

===========
Ping from Router1:
Router1#ping 192.168.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/7/20 ms
Router1#ping 10.1.1.102

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.102, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/36 ms
Router1#ping 10.1.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router1#
====================
Ping from Router2:
Router2#ping 10.1.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Router2#ping 192.168.1.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.50, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/47/48 ms
Router2#ping 192.168.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router2#
===============
Router1 Configuration:
Router1#sh run
Building configuration...
Current configuration:
!
version 11.2
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname Router1
!
enable password c
!
!
interface Ethernet0
ip address 192.168.1.60 255.255.255.0
no ip split-horizon
!
interface Serial0
ip address 192.167.3.14 255.255.255.0
no ip split-horizon
clockrate 64000
!
interface Serial1
ip address 192.167.3.15 255.255.255.0
no ip split-horizon
!
router rip
version 2
network 10.0.0.0
network 192.168.1.0
network 192.167.2.0
network 192.167.3.0
!
ip classless
!
!
line con 0
line 1 16
no exec
modem DTR-active
transport input all
dispatch-timeout 50
dispatch-character 10
dispatch-character 35
dispatch-character 58
dispatch-character 62
line aux 0
transport input all
line vty 0 3
exec-timeout 0 0
password c
login
line vty 4
no exec
password c
login
line vty 5 15
no exec
password c
login
!
end

Router1#

==============
Router2 Configuration:
Router2#sh run
Building configuration...

Current configuration:
!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname Router2
!
enable password c
!
!
interface Ethernet0
ip address 10.1.1.102 255.255.255.0
no ip split-horizon
!
interface Serial0
ip address 192.167.2.12 255.255.255.0
no ip split-horizon
!
interface Serial1
ip address 192.167.3.13 255.255.255.0
no ip split-horizon
!
router rip
version 2
network 10.0.0.0
network 192.168.1.0
network 192.167.2.0
network 192.167.3.0
!
ip default-gateway 10.1.1.1
ip classless
ip route 10.0.0.0 255.0.0.0 10.1.1.0
ip route 10.0.0.0 255.0.0.0 10.1.1.1
!
!
line con 0
exec-timeout 0 0
length 0
line 1 16
no exec
modem DTR-active
transport input all
dispatch-timeout 50
dispatch-character 10
dispatch-character 35
dispatch-character 58
dispatch-character 62
line aux 0
exec-timeout 0 0
length 0
transport input all
line vty 0 4
exec-timeout 0 0
password c
login
!
end

 
The first thing i did see directly is that on router 1 both serial interfaces are in the same subnet.

I'll draw it out now and see if i can find some more
 
Does the TFTP server have a default gateway of Router2? Since Router1 can ping 10.1.1.102, we can confirm it has a route for that subnet and that Router2 has a route back, but I'm thinking the TFTP server has no route to 192.168.1.60.

CCNP, CCDP
 
Silverblade, those serials are in different subnets. 192.167.2.0/24 and 192.167.3.0/24.

CCNP, CCDP
 
Further more. Why on router 2 the gw 10.1.1.1, what i understood is that that is you're tftp server.
then as well the line ip route 10.0.0.0 255.0.0.0 10.1.1.0 is useless.
And maybe check you're gateway on the tftp and workstation.

On a side note: Still busy getting ccna, so i could be wrong. But i think i'm a bit in the right direction here :p

Good luck with it
 
These serials ain't (R1):

interface Serial0
ip address 192.167.3.14 255.255.255.0
no ip split-horizon
clockrate 64000
!
interface Serial1
ip address 192.167.3.15 255.255.255.0
no ip split-horizon
 
Silverblade, since Router1 can ping 10.1.1.102, it proves that routing between R1 and R2 for the 10.1.1.0/24 subnet is fine. Other than a firewall rule, the only thing that's going to prevent R1 from pinging the TFTP server at 10.1.1.1 is the TFTP server's inability to route back to the 192.168.1.0 subnet.

The problem is most likely the default gateway on the TFTP server.

The 192.167.x.x config on those serial ports is interesting but none of it is relevant for this problem. Other similar points of interest are that they've disabled split horizon and are using classful route summary.

CCNP, CCDP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top