Friday, May 21, 2010 11:49 AM
I am configuring a Windows 2008 R2 server with a static IPv6 address. But after doing this there is still an autoconfigured address in addition to the one i specify. How can I disable this?
Monday, May 24, 2010 2:53 PMI believe you are talking about the link-local address; it begins with fe80. These addreses are required by RFC and cannot be disabled.
Tuesday, May 25, 2010 12:27 PM
Thanks for the answer.
I am not talking about the link-local address. The address begins with 2001, and the first 64 bits are the same that I use for the static address. Also when I run ipconfig /all it says: "Autoconfiguration Enabled . . . . : Yes"
Friday, May 28, 2010 10:21 AM
Do you mean the 2001:0000:: Teredo Unicast address? If this is it, you may check how it works if you run the following command to disable it：
Netsh interface teredo set state disabled
If this isn't it, could you please provide the IPconfig /all output from your server?
Monday, May 31, 2010 1:27 PM
Here is the output from ipconfig /all:
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter #2
Physical Address. . . . . . . . . : 00-50-56-BF-3D-DB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:700:300:24::188(Preferred)
IPv6 Address. . . . . . . . . . . : 2001:700:300:24:16a:1891:1bd3:a2f9(Preferred)
Link-local IPv6 Address . . . . . : fe80::16a:1891:1bd3:a2f9%12(Preferred)
IPv4 Address. . . . . . . . . . . : 184.108.40.206(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Default Gateway . . . . . . . . . : fe80::212:d9ff:fea6:9c7f%12
As you can see there are two addresses starting with 2001:700. The first one is set static by me, and the second one I want to get rid of.
Thursday, June 10, 2010 12:20 PM
It seems that the (old) ipv6 address is not overwritten with the (new) static address.
You can use the netsh interface ipv6 command to remove all ipv6 addresses.
Then you can configure the new ipv6 address.
To see more information, use the netsh interface ipv6 show address command.
Thursday, June 10, 2010 12:23 PM
You can use the netsh interface ipv6 reset command to remove all ipv6 addresses.
Thursday, June 10, 2010 1:33 PM
Hello Harryhi, and thanks for the tip.
Unfortunately it doesn't help me. The reset command says I need to reboot the computer, and after the reboot the manually configured address is gone, but the autoconfigured is still there.
Output from netsh interface ipv6 show address:
Interface 12: Local Area Connection 2
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Manual Preferred infinite infinite 2001:700:300:24::188
Public Preferred 29d23h58m55s 6d23h58m55s 2001:700:300:24:16a:1891:1bd3:a2f9
Other Preferred infinite infinite fe80::16a:1891:1bd3:a2f9%12
I have also tried: netsh interface ipv6 delete address "Local Area Connection 2" 2001:700:300:24:16a:1891:1bd3:a2f9
This does remove the autoconfigured address, but after a few minutes it is back.
Any more ideas?
Thursday, June 10, 2010 2:27 PM
Hello okhoel,You ask for "any more ideas", here is one:
IPv6 supports the following types of auto-configuration:
- Stateful auto-configuration. This type of configuration requires a certain level of human intervention because it needs a Dynamic Host Configuration Protocol for IPv6 (DHCPv6) server for the installation and administration of the nodes. The DHCPv6 server keeps a list of nodes to which it supplies configuration information. It also maintains state information so the server knows how long each address is in use, and when it might be available for reassignment.
- Stateless auto-configuration. This type of configuration is suitable for small organizations and individuals. In this case, each host determines its addresses from the contents of received router advertisements. Using the IEEE EUI-64 standard to define the network ID portion of the address, it is reasonable to assume the uniqueness of the host address on the link.
Regardless of how the address is determined, the node must verify that its potential address is unique to the local link. This is done by sending a neighbor solicitation message to the potential address. If the node receives any response, it knows that the address is already in use and must determine another address.
You’ll find the related configuration steps within the links.