Ccna routing and Switching Complete Study Guide

ipv6 route ::/0 fa0/1

Next, we’ll verify that we can now ping from PC1 to Server1:

C:\Users\Todd Lammle>

ping 2001:db8:3c4d:1:a14c:8c33:2d1:be3d

 

Pinging 2001:db8:3c4d:1:a14c:8c33:2d1:be3d with 32 bytes of data:

Reply from 2001:db8:3c4d:1:a14c:8c33:2d1:be3d: time<1ms

Reply from 2001:db8:3c4d:1:a14c:8c33:2d1:be3d: time<1ms

Reply from 2001:db8:3c4d:1:a14c:8c33:2d1:be3d: time<1ms

Reply from 2001:db8:3c4d:1:a14c:8c33:2d1:be3d: time<1ms

Sweet—we’re looking golden with this particular scenario! But know that it is still possible 

to have name resolution issues. If that were the case, you would just need to check your DNS 

server or local host table.

Moving on in the same way we did in the IPv4 troubleshooting section, it’s a good time 

to check into your ACLs, especially if you’re still having a problem after troubleshooting all 

your local LANs and all other potential routing issues.