Windows Vista introduces support for DHCPv6. The DHCPv6 client implementation in Windows Vista is compliant with RFC 3315. It supports 2 modes of operation: a stateless mode and a stateful mode of operation.
DHCPv6 Stateless mode is where the host uses a non-DHCPv6 method to obtain an IPv6 address, and uses DHCPv6 only to obtain other configuration parameters such as the IPv6 address of the DNS server. Typically in this mode, clients will use the IPv6 prefix from a Router Advertisement to auto-configure an IPv6 address for the network interface.
DHCPv6 Stateful mode is where a client uses DHCPv6 to obtain an IPv6 address from the DHCPv6 server along with other configuraiton parameters.
The DHCPv6 client mode of operation in Windows Vista is controlled by Router Advertisements. When the TCP/IP stack in Windows Vista receives a Media Connect event on a network interface, it sends a Router Solicitation. The Router Advertisement received in response determines the behaviour of the DHCPv6 client on that interface. If both the M & O flags in the Router Advertisement are set, the client assumes that it should DHCPv6 Stateful mode. If the O flag is set, but the M flag is not set, the DHCPv6 client uses the Stateless mode of operation.
Hope this helps you get started with deploying IPv6 in Windows Vista.
Windows Enterprise Networking
[This posting is provided "AS IS" with no warranties, and confers no rights.]
In Windows Server codenamed "Longhorn", Microsoft has introduced DHCPv6 functionality to the DHCP server.
Beta Tester's do LH Server BETA 2 já estão fazendo uso do DHCPv6 Stateless que foi projetado para se
In one of my previous posts, I had discussed details about the DHCPv6 client behaviour in Windows Vista
We are currently testing with Longhorn Beta 3 and Vista Business. We are attempting to setup DCHPv6 only with Longhorn. I have set the following M & O Flags on the Vista Client using the netsh commands, but still have yet to get my Vista client to get a IPv6 address.
Is there something I am missing either on the Server or client side that I have not setup. What would be the basic steps for this configuration to work?
I hope this is the right site to post this question.
Is it a normal behavior of Windows Vista not to release the IPv6 address when it is Restarted or during Shutdown?
We are also facing the same issues as your, like to know if you have over come the same. if yes can you please let us know the steps to resolve.
In what context of netsh do you set the M and O flags for the DHCPv6 Client (Vista)? Also how does one calculate the IPv6 DGW address of the subnet? Are there any How-to's on setting up DHCPv6 on Longhorn? I just got my test lab DC back up on the new RC0 drop this week and would like to see my Vista WS grab an IPv6 address off the DC.
How do I configure my Windows Vista machine to acquire a ipv6 address from a DHCPv6 server? Ay special configuration needed ?
Try the following on your vista machine.
In NetShell go to the interface ipv6 prompt,
netsh interface ipv6 > set interface <interface number> advertise=enabled manageAddress=enabled .
Here <interface number> is the name or id of the interface where you want to acquire IP address.
Please let me know if you still fave any problem.
Appreciate your response. Not sure what is happenening but I am unable to configure that command. I have a interface named 'ipv6'. So at the prompt I tried giving
set interface "ipv6" advertise=enabled managedAddress=enabled
I get a error 'element not found'
I tried all the combinations I could think of (with double quotes, no quotes, =) Nothing seems to help.
Is there some place I can look up the configs and the steps needed to setup a Vista dhcpv6 client
Just for some background. I am trying to do some interoperability testing between a Vista dhcpv6 client and a Cisco dhcpv6 server. Connected the 2 machines directly. The connection works fine as I was able to get a v4 address for the vista from the router. But v6 vista client doesn't seem to send a SOLICIT
I have managed to get Vista to do DHCP requests (Set M/O bits on in the RADV). I have a Windows Server 2008 eval, build 6001.
I see DHCPv6 solicit messages from the vista machine to ff02::1:2, but I don't see any responses. The ws2k8 DHCP server shows that it is running.
Any debugging tips?
What scopes have you configured at the server side?
Do you see the Solicit packet on the server side?
I see DHCPv6 solicit messages from vista.linklocal(8e16) to ff02::1:2, AND from server2k8.ll(8ced) to ff02::1:2.
I don't see any unicast traffic, and only solicit messages.
I have one scope in IPv4 (which works) and one scope in IPv6. The IPv6 scope covers the full 64 bits, based on the subnet prefix.
I got it working. Turns out that I had a dynamically assigned IPv6 address.
I had tried to make it static. I'm guessing that if you take the dynamically assigned address and set it as a static address, that somehow the system doesn't register this as a static address. At least this is what seemed to happen to me. Perhaps you can't configure a globally significant host number as a static IPv6 address?
When I set the static address to be prefix::200, it took and DHCPv6 started to work.
It would be nice if DHCPv6 had some kind of signal in the UI or logs that indicated this.
Thanks for your help.