Routing Problem

[timothha22]

I am having a problem routing between my two networks. These networks are connected via a 1.5 PTP line. We have a Cisco 1700 on one side and a Cisco 2600 on the other. One network is a 192.168.1.0 255.255.255.0 the other is 10.1.0.0 255.255.0.0 network. I can ping certain machines on the 192.168.1.0 network but not others. They all have their default gateway setup to a linux box with a route added to get to the 10.1.0.0 network pointed to the router. The same is the case on the 10.1.0.0 network. I can ping 192.168.1.1 from the 10's network but I cannot ping 192.168.1.4. The same goes with the 192.168 network. Does anyone have any idea what this might be?

10's network router config.

version 12.1
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname HomeOfficeP2P
!
enable secret 5 $1$QySv$T75U1lsUmTI1agAA5ZeIP1
!
!
!
!
!
memory-size iomem 25
ip subnet-zero
no ip domain-lookup
!
!
!
!
interface Serial0
description connected to UnknownDevice
ip address 172.16.2.1 255.255.255.0
service-module t1 remote-alarm-enable
!
interface FastEthernet0
description connected to Internet
ip address 10.1.125.3 255.255.0.0
speed auto
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.16.2.2
ip route 172.16.2.0 255.255.255.0 172.16.2.2
ip route 192.168.1.0 255.255.255.0 172.16.2.2
no ip http server
!
access-list 20 permit any
snmp-server engineID local 0000000902000002B9CC1D6C
snmp-server community public RO
!
line con 0
exec-timeout 0 0
password cisco
login
transport input none
line aux 0
line vty 0 4
password cisco
login
!
end


192 router config.



User Access Verification

Password:
Password:
COLO>ena
Password:
COLO#show run
Building configuration...

Current configuration : 822 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname COLO
!
enable secret 5 $1$dOJs$H2p45vBXVg37ULs0qjrg.0
enable password 7 10591B12071E151F0509
!
ip subnet-zero
!
!
no ip domain-lookup
!
!
!
!
interface FastEthernet0/0
ip address 192.168.1.10 255.255.255.0
speed auto
half-duplex
!
interface Serial0/0
description connected to HOMO
ip address 172.16.2.2 255.255.255.0
service-module t1 remote-alarm-enable
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.1
ip route 10.1.0.0 255.255.0.0 172.16.2.1
ip route 172.16.2.0 255.255.255.0 172.16.2.1
no ip http server
!
snmp-server community public RO
snmp-server enable traps tty
!
line con 0
exec-timeout 0 0
password 7 045802150C2E
login
line aux 0
line vty 0 4
password 7 05080F1C2243
login
!
end

 

[JOAMON]

Question:
Router COLO...FastEthernet 0/0 connects to what?
Need:
Home Router:
interface serial0
ip nat inside
encapsulation ppp
no keepalive

interface fastethernet0
ip nat inside

Delete:
ip route 172.16.2.0 255.255.255.0 172.16.2.2
ip route 192.168.1.0 255.255.255.0 172.16.2.2
Not needed as default route will work for these

Need:
COLO Router:
Interface Serial 0/0
ip nat inside
encapsulation ppp
no keepalive
service-module t1 clock source internal

Most service providers do not clock PTP t1 circuits so you must do so at one end.

I would also Enable RIP as follows:
Router COLO:
router rip
version 2
network 192.168.1.0
network 172.16.0.0
no auto-summary
passive-interface fastethernet0/0

Router HOME:
router rip
version 2
network 172.16.0.0
network 10.0.0.0
no auto-summary

Hope this helps : )

 

[timothha22]

I think that may help. The COLO Router connects into a 3com switch in the local network at our colo facility. I will put all of this into place and let you know how it works out.

Thank You For Your Help.

Tim

 

[JOAMON]

After the 3com switch does it connect into a firewall device or something?

 

[timothha22]

Actually after the 3com switch it connects into the local network. This is a private line between two networks. I am using my firewall to tell the network how to get to the 10's network.

Hope this is enough info. It will be tomorrow before I can try the fix.

Tim

 

[JOAMON]

In that case then do not need the passive-interface in the rip statement. Only meant to not broadcast routing announcements to the internet.