Dynamic Host Configuration Protocol version 6: Although IPv6’s stateless address autoconfiguration removes the primary motivation for DHCP in IPv4, DHCPv6 can still be used to statefully assign addresses if the network administrator desires more control over addressing. It can also be used to distribute information which is not otherwise discoverable; the most important case of this is the DNS server.

In a network environment, you deploy the Dynamic Host Configuration Protocol version 6 (DHCPv6) solution. This solution uses Internet Protocol version 6 (IPv6). However, on a Windows Vista-based or Windows Server 2008-based DHCP client computer, you may find that some network-related parameters are configured incorrectly. Therefore, you cannot access the network correctly.

Internet Protocol version 6: A network layer protocol for packet-switched internetworks. It is designated as the successor of IPv4, the current version of the Internet Protocol, for general use on the Internet. The older IPv4 only supports 4.3 billion addresses, where IPv6 can support 3.4×10 to the 28th power.

Remote access clients that are running Windows Vista cannot access Routing and Remote Access Service servers that use IPv6 or the computers behind the servers.

Accessing shares or mapping drives using IPv6 addresses will fail.

Examples of failing commands:

net use * \\2001:db8:0:1::9\c$ ()

Or try to access the address through Start->Run.

\\2001:db8:0:1::9\c$ ()

The error message is:

System error 67 has occurred. The network name cannot be found.

When you use Event Viewer to view an event log that contains Microsoft Internet Protocol version 6 (IPv6) addresses, the IPv6 addresses do not display correctly in the descriptions of events. For example, an element of the event log payload replaces the scope ID part of the IPv6 address. In some cases, the multiple replacements are repeated several times in the IPv6 address.