Troubleshooting IPv6 (Windows Embedded CE 6.0)
1/6/2010
What problem are you having?
| Problem | Cause and solution |
|---|---|
The Link Local address is not available. |
Cause: The network interface card (NIC) may not be recognized. Solution: Verify that the NIC is inserted correctly. Verify that you have IPv4 connectivity. Verify that it is recognized and initialized. |
A router is not advertising itself as a default router. |
Cause: A computer running Windows CE .NET 4.1 and later that is being used as an IPv6 router will not advertise itself as a default router unless it is configured with a default route (::/0) that is configured to be published. Solution: Add a default route to the router computer and configure it to be published. See Also: Adding an IPv6 Route |
A default route is not present on the host. |
Cause: A computer running Windows CE .NET 4.1 and later that is being used as an IPv6 router will not advertise itself as a default router unless it is configured with a default route (::/0) that is configured to be published. Solution: Add a default route to the router computer and configure it to be published. See Also: |
Address has unexpected interface identifier. |
Cause: A local router is configured to advertise a global prefix. By default, a temporary address that is based on the global prefix is automatically configured. Solution: Disable temporary addresses. See Also: TCP/IPv6 Troubleshooting Tools IPv6; |
Off-link routes are in the routing table. |
Cause: When a router running Windows CE .NET 4.1 and later advertises off-link prefixes, it sets a reserved bit in the Prefix Information option of the Router Advertisement message. When a host computer running Windows CE .NET 4.1 and later receives an off-link prefix with this bit set, it adds a route to its routing table for the advertised prefix with the forwarding address of the advertising router. Solution: None. This is intended. See Also: Maintaining Route Tables for IPv6 |
Ping fails Echo Request messages when specifying a link-local destination. |
Cause: The scope ID is not specified. Solution: This is a common problem when a link-local destination address is used. Link-local addresses are often configured automatically for multiple interfaces. To specify the exact interface over which to send Echo Request messages, use the ping Address%ScopeID syntax where ScopeID is the interface identifier for the interface over which the ping traffic is sent. See Also: |
Unable to reach other 6to4 sites or the test Internet (6bone) by using the 6to4 router. |
Cause: Your firewall or Internet router is dropping IPv4 traffic that has the IP Protocol field value set to 41. Solution: All IPv6 traffic that is encapsulated (tunneled) inside of an IPv4 header has the IPv4 Protocol field in the header set to 41. IPv6 tunneled traffic includes traffic that uses 6to4 addresses. To allow IPv6 tunneled traffic to be forwarded, configure your firewall or Internet router to pass IPv4 traffic that has the Protocol field set to 41. Cause: You are unable to resolve the DNS name 6to4.ipv6.microsoft.com. Solution: By default, the IPv6 Helper service attempts to first resolve the name 6to4.ipv6.microsoft.com to its IPv4 addresses and then chooses a relay router. If you cannot resolve the name 6to4.ipv6.microsoft.com, a relay router is not configured and you cannot reach any locations on the test Internet (6bone). Type ping 6to4.ipv6.microsoft.com to determine whether you can resolve the name 6to4.ipv6.microsoft.com. Cause: You do not have the correct route. Solution: View the routing table using the ipv6 rt command. You should see a 2002::/16 -> 3 route. This route causes all 6to4 traffic to be sent by using the 6to4 tunneling interface. Cause: You do not have the correct address. Solution: Verify that you have a 6to4 address assigned before attempting to reach a destination. For example, without a 6to4 address, you might be using a link-local address to reach a 6to4 global address. Use the display of the ipv6 if command to determine configuration details for your address. |
See Also
Concepts
Converting to IPv6
Diagnosing Connections
IPv6 RFCs and Internet Drafts