Newb routing problem 2x1941's

[gregbaiocchi]

I have 2x 1941's in my home lab with one client on each router. no net connection. I can ping from 1.10 to 2.10 but not the other way around. Any ideas? this is driving me nuts. I can ping all the way to gi0/1 through both s0/1's

R1 has a W10 client on it 192.168.1.10 255.255.255.0

R2 has a Pi on it 192.168.2.10 255.255.255.0 

Router1#show run
Building configuration...

Current configuration : 1464 bytes
!
! Last configuration change at 02:36:02 UTC Thu Apr 6 2017
!
version 15.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router1
!
boot-start-marker
boot-end-marker
!
no aaa new-model
!
no ip domain lookup
ip cef
no ipv6 cef
multilink bundle-name authenticated
!
cts logging verbose
!
license udi pid xxx sn xxx
!
redundancy
!
ip ssh time-out 50
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
no ip address
ip virtual-reassembly in
shutdown
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 192.168.1.1 255.255.255.0
ip virtual-reassembly in
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
shutdown
clock rate 2000000
!
interface Serial0/0/1
ip address 192.168.3.1 255.255.255.0
clock rate 64000
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 192.168.2.0 255.255.255.0 Serial0/0/1
!
logging host 198.105.254.130

---------------------------------------------------------------------------------------------------------------------------------------------

Building configuration...

Current configuration : 2303 bytes
!
! Last configuration change at 02:41:56 UTC Thu Apr 6 2017
!
version 15.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router2
!
boot-start-marker
boot-end-marker
!
no aaa new-model
!
no ip domain lookup
ip cef
no ipv6 cef
multilink bundle-name authenticated
!
cts logging verbose
!
license udi pid xxx sn xxx
!
redundancy
!
ip ssh time-out 50
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
no ip address
ip virtual-reassembly in
shutdown
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 192.168.2.1 255.255.255.0
ip virtual-reassembly in
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
shutdown
clock rate 2000000
!
interface Serial0/0/1
ip address 192.168.3.2 255.255.255.0
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 192.168.1.0 255.255.255.0 Serial0/0/1
!
logging host 198.105.254.130
!
control-plane
!
line con 0
logging synchronous
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password cisco
login
transport input none
!
scheduler allocate 20000 1000
!
end

[Dennis Mink]

from your 2.10 test the following:

see if you can ping the 2.1  

see if you can ping then serial interface of the router

see if you can ping the serial interface of the remote router

see if you can ping the 1.1 on the remote router,

see what works and what doesnt and isolate the problem by braking the path up

please rate if useful

[gregbaiocchi]

forgot to include that...I'm exhausted. yes, I can ping 2.1,3.2,3.1,1.1. so everything but the client

[Dennis Mink]

can you ping 2,10 from 2.1

and 2.10 sourced from 3.2?

[gregbaiocchi]

yes, everything pings except 2.10 to 1.10

[bogdan_butucel]

Can you ping 1.10 from Router 2 using the source of 2.1 ?

[gregbaiocchi]

yes.

Router2#ping
Protocol [ip]:
Target IP address: 192.168.1.10
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.2.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:
Packet sent with a source address of 192.168.2.1

192.168.2.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:
Packet sent with a source address of 192.168.2.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max

[paul driver]

Hello

Turn off any software firewall on the windows clients or allow them to receive echo-reply

res
Paul

[gregbaiocchi]

tried that.  I can ping from r1 to the 1.10 client but not from client2.10 to client 1.10

[gregbaiocchi]

I just swapped IPs of the clients and swapped their ports...same thing. I really doubt its a firewall issue.

[Jon Marshall]

So when you swapped IPs could you then ping from 1.10 to 2.10 or not.

Jon

[gregbaiocchi]

Yes...exact same problem as before.

[gregbaiocchi]

still unsolved...should I post this somewhere else?

[paul driver]

Hello

As you are specifiying static routes towards an interface instead of next hop then you'll need proxy arp enabled on each interface your statics point to

so try enabling proxy arp

res

Paul

[gregbaiocchi]

Thanks for the reply.  I set ip proxy-arp on every interface...same issue