cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3258
Views
0
Helpful
13
Replies

Please help! The ping isn't working properly in my network.

AJSilver
Level 1
Level 1

The pinging works if it's between the PCs however when doing the following, it doesnt work:

  • PCs pinging Aimee router gig port 10.87.63.254 is a success however it fails and times out when pinging gig port 10.87.127.254.
  • DNS server pinging to PCs = Request timed out. 
  • DNS server pinging to laptop/smartphone = destination host unreachable.
  • DNS server pinging to Cloud server = destination host unreachable.
  • DNS server pinging to ISP Serial port 10.87.128.1 works however when pinging to its Gig port 11.1.1.1 then it says destination host unreachable.

AJSilver_1-1678206809007.png

*********************************************************************************
UPDATE:

Thanks so much everyone for helping! I've now got full connectivity everywhere.

How connectivity to VLAN got fixed =
Some small changes I made to the ip addresses in my VLAN. Also the ISP router wasn't announcing the network 11.0.0.0 properly so i managed to sort that out by setting the Aimee router's Serial port to the network 11.0.0.0 first. Then because the cloud server Fa-port was set down, I fixed it by just re-wiring the copper-cross-over wire again and it worked.

How connectivity to wireless LAN C got fixed = 
A simple change I did to the Aimee router. After coding the following, the IP addresses was set correctly by the DHCP and this enabled the full connectivity to work:
        (config) ip dhcp excluded-address 10.87.255.254

Updated image:

AJSilver_0-1678281637900.png

 

 

5 Accepted Solutions

Accepted Solutions

balaji.bandi
Hall of Fame
Hall of Fame

Couple of the things you need to check here on the switch.

- is the switch acting as Layer 2 ? or Layer 3?

- what is the PC gateway ? is this point to 0.1 or 63.254 ?

- how is your config switch port config -  connected to router

- can you post

 show run

(from switch and Router) (if possible all the device show run)

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

View solution in original post

Pinging to PCs also worked but only 4/5 success.  - if you do one more time you get success 5/5 (you see normally intial packet los for the first time).

If you running RIP as IGP, ISP router not anouncing the network 11.1.1.1/30 - so add this network anouncement on ISP router.

Cloud server configured 88.44.22.2/30 ? where is the gateway configured for this ?

ISP router you need to replace 11.1.1.1/30 with 88.44.22.1/30  or reconfigure Cloud server with IP 11.1.1.2/32 gateway 11.1.1.1 to work.

The other destinations did not work at all from the router.  - give example which was failed ?

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

View solution in original post

RIP when you issue a command network that might have already taken in to routing table

you can check on Aimee router

show IP route

(you should see 11.0.0.0 supernet there)

cloud router - try rebooting after the IP change.  see not sure what image you using as cloud router.

 

When pinging from Aimee router it fails in the following: 

  • Aimee router pinging to Laptop/smartphone = 0/5 success  - the IP you configured not in the network they Link Local, configured correct IP address range.
  • Aimee router to ISP = 0/5 success  -  Aimee router and ISP router should ping if the interface serial up.
  • Aimee router to Cloud server = 0/5 success  - this not work until your cloud router interfaceup

When trying to ping from switch then it fails in following:

  • Switch to DNS server = request timed out  - what is the outcome DNS Server to gateway ping (fix that )
  • Switch to laptop/smartphone = request timed out. - this not work as mentioned above.
  • Switch to ISP router port Se0/0/0 = 5/5 Success.  But, ping to port gig0/1 = 0/5 success.  - you need to fix and make sure interface up to ping.
  • Switch to Cloud server = 0/5 success - same as above.
  •  

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

View solution in original post

I am not familiar with PT, how the AP configuration to be done on PT

high level you have routing issue and make sure you have right DHCP Scope and right default gateway for the pool for the devices to work.

check this video :

https://www.youtube.com/watch?v=-E4yivI26SY

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

View solution in original post

169.254.0.0/16 (169.254.0.0 – 169.254.255.255)
These addresses are “link local,” which means packets with these addresses are sent out to the network, but should never be forwarded to other parts of the network. You’ll often see addresses from this range if a device is unable to get an address using DHCP. Then it simply takes an address from this range and uses it to try to at least communicate locally.

use Private Ip range for your DHCP and set Gateway according to that network

View solution in original post

13 Replies 13

balaji.bandi
Hall of Fame
Hall of Fame

Couple of the things you need to check here on the switch.

- is the switch acting as Layer 2 ? or Layer 3?

- what is the PC gateway ? is this point to 0.1 or 63.254 ?

- how is your config switch port config -  connected to router

- can you post

 show run

(from switch and Router) (if possible all the device show run)

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Thank for the fast reply!

I'm not quite sure how to check if switch is acting as layer 2 or 3. The PC gateway however is .63.254

Ive also attached a document showing all the

show runs

of the switch, router and the ISP router.

All the routerr configure ip routing

config t

!

ip routing

!

Once this enabled, from Ainee router, try to ping all the destination before you try from PC - is that working ?

and post from all routers :

show ip route 

show ip interface brief

show ip arp

show cdp neighbour.

also from PC traceroute to 11.1.1.1

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

i enabled ip routing on all the routers. 

Then i tried the ping to all destination from the Aimee router. It worked 5/5 success only on the DNS server. Pinging to PCs also worked but only 4/5 success. 

The other destinations did not work at all from the router.

The traceroute from switch to 11.1.1.1 printed the below:

AJSilver_0-1678213121427.png

I also attached a document showing the information from the all the routers as requested.

 

Pinging to PCs also worked but only 4/5 success.  - if you do one more time you get success 5/5 (you see normally intial packet los for the first time).

If you running RIP as IGP, ISP router not anouncing the network 11.1.1.1/30 - so add this network anouncement on ISP router.

Cloud server configured 88.44.22.2/30 ? where is the gateway configured for this ?

ISP router you need to replace 11.1.1.1/30 with 88.44.22.1/30  or reconfigure Cloud server with IP 11.1.1.2/32 gateway 11.1.1.1 to work.

The other destinations did not work at all from the router.  - give example which was failed ?

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Pinging to the PCs from Aimee router now works and also pinging to the DNS server works too, thank you.

About the ISP router, i'm not sure how to make it announce the network 11.1.1.1/30. I tried writing the below but didn't work.

AJSilver_0-1678221488165.png

I have reconfigured the cloud server's default gateway and ip address but i noticed the below says link is down? Do you know how to make the link go up?

AJSilver_2-1678221917973.png

When pinging from Aimee router it fails in the following:

  • Aimee router pinging to Laptop/smartphone = 0/5 success
  • Aimee router to ISP = 0/5 success
  • Aimee router to Cloud server = 0/5 success

Also when trying to ping from PC to DNS server, laptop, smartphone, ISP, and cloud server then it says request timed out.

When trying to ping from switch then it fails in following:

  • Switch to DNS server = request timed out
  • Switch to laptop/smartphone = request timed out.
  • Switch to ISP router port Se0/0/0 = 5/5 Success.  But, ping to port gig0/1 = 0/5 success. 
  • Switch to Cloud server = 0/5 success

 

 

 

 

 

 

RIP when you issue a command network that might have already taken in to routing table

you can check on Aimee router

show IP route

(you should see 11.0.0.0 supernet there)

cloud router - try rebooting after the IP change.  see not sure what image you using as cloud router.

 

When pinging from Aimee router it fails in the following: 

  • Aimee router pinging to Laptop/smartphone = 0/5 success  - the IP you configured not in the network they Link Local, configured correct IP address range.
  • Aimee router to ISP = 0/5 success  -  Aimee router and ISP router should ping if the interface serial up.
  • Aimee router to Cloud server = 0/5 success  - this not work until your cloud router interfaceup

When trying to ping from switch then it fails in following:

  • Switch to DNS server = request timed out  - what is the outcome DNS Server to gateway ping (fix that )
  • Switch to laptop/smartphone = request timed out. - this not work as mentioned above.
  • Switch to ISP router port Se0/0/0 = 5/5 Success.  But, ping to port gig0/1 = 0/5 success.  - you need to fix and make sure interface up to ping.
  • Switch to Cloud server = 0/5 success - same as above.
  •  

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Thank you so much, the pinging now seems to work everywhere except the laptop and smartphone. 

For the laptop/smartphone it says 'host not reachable'. I tried to create dhcp server on the Aimee router and tried to bind the laptop/smartphone ip network but when i use the command

show ip dhcp binding

then its not showing anything.

AJSilver_0-1678229317633.png

How can I fix this?

 

Good progress, nice pickup like it the way its going 

as I mentioned 169.X is Link Local IP address? not sure where this device get IP address from DHCP ? do you have DHCP Server  any where ?

are you able to ping AP IP address 10.187.192.1 ?

balajibandi_0-1678229645687.png

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

The smartphone and laptop are allocated ip addresses by the DHCP.

I have DHCP server in the Aimee router as below:

  • show ip dhcp pool

    AJSilver_0-1678269708469.png
  • show ip dhcp binding

    AJSilver_1-1678269811137.png

     

  • show run

    AJSilver_2-1678270048759.png
    AJSilver_3-1678270303940.png

     

I'm able to ping from switch to router aimee port gig0/2 10.87.255.254 with 5/5 success but I get 0/5 success if trying to ping to the laptop/smartphone.

 

I am not familiar with PT, how the AP configuration to be done on PT

high level you have routing issue and make sure you have right DHCP Scope and right default gateway for the pool for the devices to work.

check this video :

https://www.youtube.com/watch?v=-E4yivI26SY

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

169.254.0.0/16 (169.254.0.0 – 169.254.255.255)
These addresses are “link local,” which means packets with these addresses are sent out to the network, but should never be forwarded to other parts of the network. You’ll often see addresses from this range if a device is unable to get an address using DHCP. Then it simply takes an address from this range and uses it to try to at least communicate locally.

use Private Ip range for your DHCP and set Gateway according to that network

chesterr
Level 1
Level 1

Hello,

All of your problems involve router Aimee. Show output from commands mentioned by balaji.bandi and show running-config from Aimee router.