Reasons for unsuccessful ping

Question 1

Give reasons for unsuccessful ping responses (1 of 7)

Answer 1

Router access control list (ACL) is blocking the ICMP traffic: The router may have an ACL configured that specifically blocks ICMP traffic, preventing the ping from reaching PC B.

Question 2

Give reasons for unsuccessful ping responses (2 of 7)

Answer 2

Router’s interface towards PC B is down (Ethernet ports on routers default to SHUTDOWN): If the router’s interface towards PC B is down, it will not be able to forward the ping request to PC B as the routeing table will NOT contain the directly connected routes.

Question 3

Give reasons for unsuccessful ping responses (3 of 7)

Answer 3

Router’s firewall is blocking the ICMP traffic OR ICMP inspection might need to be enabled: The router may have a firewall feature that is blocking the ICMP traffic.

Question 4

Give reasons for unsuccessful ping responses (4 of 7)

Answer 4

Incorrect default gateway configuration: If PC A has an incorrect default gateway configured, it will not be able to reach PC B through the router.

Question 5

Give reasons for unsuccessful ping responses (5 of 7)

Answer 5

Incorrect IP address or subnet mask configuration on the router or PC A: If the IP address or subnet mask is incorrectly configured on the router or PC A, it will not be able to reach PC B.

Question 6

Give reasons for unsuccessful ping responses (6 of 7)

Answer 6

Router’s virtual LAN (VLAN) configuration is preventing communication: If PC A and PC B are on different VLANs and the router is not configured to allow communication between them, the ping will not reach PC B.

Question 7

Give reasons for unsuccessful ping responses (7 of 7)

Answer 7

Router’s routing table is not updated: If the routing table on the router is not updated or has incorrect information, it will not be able to forward the ping request to PC B.