6 Replies Latest reply on Jun 16, 2013 9:20 PM by pileus

    3400 router cant ping itself

    pileus New Member

      I have two routers connected via fractional t1. The router in the diagram R2 cant ping its Ethernet port 192.168.15.1 but it can ping its t1 port 192.168.1.2. when I attempt to ping 192.168.15.1 from the 192.168.10.0 segment it expires in transit at 192.168.1.2. I am seeking direction to solve. I want to eventually connect that segment to the internet.

       

       

      mii-new-ip v2 q.jpg

      ip subnet-zero

      ip classless

      ip routing

      !

      event-history on

      no logging forwarding

      logging forwarding priority-level info

      no logging email

      ip forward-protocol udp netbios-ns

      ip forward-protocol udp netbios-dgm

      ip forward-protocol udp netbios-ss

      !

      ip policy-timeout tcp all-ports 600

      ip policy-timeout udp all-ports 60

      ip policy-timeout icmp 60

      !

      !

      !

      ip dhcp-server pool

        network 156.144.15.0 255.255.255.0

        dns-server 12.159.248.1 12.159.248.2

        default-router 156.144.15.1

      !

      interface eth 0/1

        half-duplex

        speed 10

        ip address  156.144.15.1  255.255.255.0

        ip helper-address  156.144.14.255

        no shutdown

      !

      interface t1 1/1

        tdm-group 1 timeslots 1-24 speed 64

        no shutdown

      !

      interface ppp 1

        ip address  192.168.1.2  255.255.255.252

        no shutdown

        cross-connect 1 t1 1/1 1 ppp 1

      !

      ip route 0.0.0.0 0.0.0.0 192.168.1.1

      !

      no ip snmp agent

        • Re: 3400 router cant ping itself
          levi Employee

          pileus:

           

          Thank you for asking this question in the Support Community.  Is the configuration you posted above taken from the "R2" unit from the diagram?  If so, it appears the IP address is not configured for 192.168.15.1.  It appears to be configured for "ip address  156.144.15.1  255.255.255.0."  Do you know if that is just a mistake in the configuration example above?  If the IP address is actually 192.168.15.1, another thing to keep in mind is the physical interface has to be connected and "UP." 


          Therefore, make sure you are pinging the correct IP address, and that the interface where that IP address is assigned is connected and "UP."

           

          I hope that makes sense, but please do not hesitate to reply to this post with any additional questions or information.  I will be happy to help in any way I can.

           

          Levi

          1 of 1 people found this helpful