Announcement

Collapse
No announcement yet.

CAN PING NETWORK UNTILL ROUTER PLUGGED IN

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • CAN PING NETWORK UNTILL ROUTER PLUGGED IN

    I have 2 locations, both have 2 dell 2724 switches unmanaged, and 2 dell N2024 3 layer switches. Both N2024 switches are set up identical except the one I am having a problem with(Location 2),

    Location 2 connected to SAN 192.168.0.10
    Only difference between location 2 and 1 is I have a ASA behind the 1811, ASA no dhcp, only firewall
    Cisco 1811 Router is 10.1.16.0
    192.168.1.10, IT dept computer 10.1.16.6(static address in advanced tcp/ip 192.168.1.64), and vmware switches connected to 2024s
    1811>Dell 2724>N2024 are connected
    All 10.1.16.0 computers plugged into 2724s, can ping 10.1.16.6, but 10.1.16.6 cannot ping 192.168.1.10.

    OK ..
    So I have a cable going from the 2724s to the 2024s just like Location 1 and 10.1.16.6 can ping router 10.1.16.1, but cannot ping 192.168.1.10(both on same switch 2024). Now if I unplug the cable connecting the 2724 to the 2024, 16.6 still wont ping 192.168.1.10, but if I unplug the 10.1.16.6 cable from switch going to the computer, wait for light to go off on switch , plug back in, the 16.6 can ping 192.168.1.10. Now if I plug the cable connecting the 2724 to the 2024 back in, it will still ping. If I unplu plug 10.1.16.6 , then back in, wont ping.

    I did this 3 times to verify. So I took a regular Linksys 8 port switch, plugged 192.168.1.10, vlan switches, and the 10.1.16.6 into it, I was able to ping 192.168.1.10 just fine.
    Only thing I could think of was the 1811 somehow causing this problem. So I plugged everything back as was, unplugged 1811 from 2724, unplugged 16.6, plugged 16.6 back in and it could ping 192.168.1.10. But i dont see how the 1811 could be causing this problem.

    Hope I explained clearly, pretty confusing.

    Any thoughts would be great

  • #2
    Originally posted by Kobe 310
    Cisco 1811 Router is 10.1.16.0
    REALLY!!, your router has the IP of 10.1.16.0

    Make a drawing of the network connections and post it. I find you description confusing. You may not since you actually know it.

    Man read your post OUT LOUD and see if you can understand it.
    Last edited by biggles77; 27th August 2015, 11:25.
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      yea i know where you are coming from! I did read it aloud, honestly i did. Didn't want to post this because of the confusion. Put it the best way i could, spent about an half hour on post and making adjustments to be as clear as possible. Drawing would be best.

      I meant to say router is 10.1.16.0 network
      Last edited by Kobe 310; 27th August 2015, 20:34.

      Comment


      • #4
        Here is the Drawing, thanks
        Attached Files

        Comment


        • #5
          Are the clients configured with multiple gateways or static routes?

          Can you post the running config from the routers and switches (attach as txt files and clearly name them) as well as an ipconfig/all from a client machine?
          Regards,
          Jeremy

          Network Consultant/Engineer
          Baltimore - Washington area and beyond
          www.gma-cpa.com

          Comment


          • #6
            Originally posted by JeremyW View Post
            Are the clients configured with multiple gateways or static routes?
            no

            Originally posted by JeremyW View Post
            Can you post the running config from the routers and switches (attach as txt files and clearly name them) as well as an ipconfig/all from a client machine
            yes, thanks!

            On the Run-config for the 1800, you'll see the route pointing to 10.1.14.1, that is an ASA behind the 1800, it'
            s used as a firewall only.

            I have just noticed that I am getting a duplicate address error, no matter what ip address I use, in the advanced tab of the local area connection, on the client machine,192.168.1.12,13,67,89, etc. There isn't a router for the 192.168.1, and there is only 4 address being used in that range.
            Attached Files
            Last edited by Kobe 310; 1st September 2015, 16:09.

            Comment


            • #7
              Oh, I completely missed that the clients have the 192.168.1.x address on their adapter. OK, in that case can you do a route print and arp -a -N 192.168.1.x (whatever the IP address is) and post the results when it's working and when it's not working?
              Regards,
              Jeremy

              Network Consultant/Engineer
              Baltimore - Washington area and beyond
              www.gma-cpa.com

              Comment


              • #8
                That's cool, this is at a different location, not sure when I can get there to make it work, I'll keep you posted. I ran those commands when not working. The arp -a -N 192.168.1.10 didn't work. I did run arp -a 192.168.1.10 and posted that.

                Thanks Jeremy
                Attached Files
                Last edited by Kobe 310; 1st September 2015, 20:43.

                Comment


                • #9
                  If you were running it from the computer with the 192.168.1.36 address configured then you should run arp -a -N 192.168.1.36. (this command lists the arp entries for that adapter)

                  In the route table I see no entry for the 192.168.1.0 network. So my guess is this is due to the duplicate on the network. Track that down or try a different IP and see if that works.
                  Regards,
                  Jeremy

                  Network Consultant/Engineer
                  Baltimore - Washington area and beyond
                  www.gma-cpa.com

                  Comment


                  • #10
                    when I run the arp -a -N 192.168.1.36 I get

                    C:\Users\Admin>arp -a -N 192.168.1.36
                    ARP: bad argument: 192.168.1.36

                    I attached file from when I run arp -a -N from the 10.1.16.6,
                    Attached Files

                    Comment


                    • #11
                      now if I run those arp commands on the computer at the other site 10.1.10.6 and 192.168.0.67, it works, and I see the 192.168.0.67, the vlan nic cards 192.168.0.111,112, and the SAN 192.168.0.10, on arp tables for both of those addresses.

                      Comment


                      • #12
                        i was able to catch the arp. i forgot to use the advanced tab ip address, 192.168.1.36, i used the ip4 address 10.1.10.6. I hope with what i got it would be the same results. Please let me know if i need to do it with the advanced tab ip. with the .6, the 192.168.1.10 shows up.

                        One ARP was with the router unplugged pinging from the 10.1.10.6, and the other is when i plugged the router back in, still pinging.

                        Thanks
                        Attached Files

                        Comment


                        • #13
                          Hi, you could give the below commands a try and test one at at time and check the result.
                          As long as you don't save the config on the router, or make the route persistent on the windows machine the changes won't survive a reboot.

                          On the 1800 in global config.
                          ip route 192.168.1.0 255.255.255.0 FastEthernet1

                          On the client which has IP 10.1.16.6
                          Route add 192.168.1.0 MASK 255.255.255.0 10.1.16.6
                          Please remember to award reputation points if you have received good advice.
                          I do tend to think 'outside the box' so others may not always share the same views.

                          MCITP -W7,
                          MCSA+Messaging, CCENT, ICND2 slowly getting around to.

                          Comment


                          • #14


                            Awesome, it worked!!!

                            Question, I'm curious as to why after I put the command in the Cisco Router, and having an ip address of 192.168.1.63 in the Advanced Tab of the client, it won't ping unless I run that command on each client.

                            Is there a way that I don't have to do that?

                            Thanks

                            Comment


                            • #15
                              Kobe, you have an IP conflict on your network. Windows is detecting it and not allowing the client(s) to use the configured 192.168.1.x addresses. The commands uk_network suggested have you routing to the 192.168.1.x network through the router. So the clients are sending from the 10.1.16.x address and not their 192.168.1.x address.

                              If you resolve the conflicts you should be able to do away with the static routes.

                              Have you tried configuring different IP addresses for the clients?
                              Regards,
                              Jeremy

                              Network Consultant/Engineer
                              Baltimore - Washington area and beyond
                              www.gma-cpa.com

                              Comment

                              Working...
                              X