In Windows Server 2008 (WS08), Microsoft has introduced DHCPv6 functionality to the DHCP server.
In Windows Server 2008 (previously known as "Longhorn" Server) Beta 2, we released the DHCPv6 Stateless Server functionality. In Beta 3, we are introducing the DHCPv6 Stateful Server functionality. As I explained in my previous post DHCPv6 behaviour in Windows Vista, in the DHCPv6 stateless mode clients use DHCPv6 only to obtain network configuration parameters other than the IPv6 address. In this scenario, clients configure an IPv6 address through a non-DHCPv6 based mechanism (possibly through IPv6 address auto-configuration based on the IPv6 prefixes included in Router Advertisements, or through static configuration.) In the DHCPv6 stateful mode, clients acquire both the IPv6 address as well as other network configuration parameters through DHCPv6.
In WS08 Beta 3, our Beta and TAP customers will have access to the following DHCPv6 features:
If you are interested in evaluating the Windows DHCPv6 server for your IPv6 deployment, we would love to have you participate in the Longhorn Server Beta program. If you are a Windows Server 2008 TAP customer, you will of course soon have access to the next IDS build in February which will contain the DHCPv6 Stateful server. Send me an email if you would like to participate in our beta program.
Windows Enterprise Networking
Beta Tester's do LH Server BETA 2 já estão fazendo uso do DHCPv6 Stateless que foi projetado para se
La implementación de DHCPv6 en Windows Server 2008 es un área en la cual las bondades de red han sido
Recently, I've been seeing a lot of articles online claiming that IPv6 will make networks more secure because it makes port scanning harder. One example is this blog entry from a Microsoft employee who works on MS' DHCPv6 server team....
How do I configure Windows 2008 DHCP server to act as a stateless DHCP server. I added the DNS server address as well as the domain list. However, the server is not responding to DHCPv6 Information-request from the client.
Could you confirm the issue reported as MS Connect ID 45620 violates RFC 3646, thus this is a bug of Windows Server 2008?
Hello DHCP team. I'm currently doing research about DHCPv6. Until now, i'm able to lease IPv6 address from Windows Server 2008 and CISCO router 2800 series to Windows Vista client using eui-64 prefix length address. My question is, are both Windows Server 08 and CISCO router support extended prefix length? One more thing, what is the right way or other way to configure DHCPv6 in CISCO router? The steps that i do is assigned an IPv6 address in f/a interface and issued "IPv6 unicast routing" command, the router really do advertise IPv6 address. But is that a correct way? Please help me.
Windows Server 2008 supports only 64 bit prefix length. We are not in a position to provide guidance on Cisco Router configuration.
Hello again DHCP team. Just a short question, is there another approach to configure DHCP in the network other than via server or router?
As the 3rd bullet mentioned, how do we configure Vista client to specifically get non-temporary or temporary address from the DHCPv6 server?
Microsoft DHCP Server does not lease out temproary V6 address.
Necesito saber que version especifica de windows server soporta el servicio de DHCPv6????
Windows Server 2008 y Windows Server 2008 R2, el apoyo DHCPv6.
1. it is possible to switch Windows Server 2008 dhcpv6 from stateful to stateless after DHCPv6 service installation ?
2. How can I send "O" so other-config flag from Windows Server 2008 co vista client ?
Hi Bruce CJ,
I'm trying to manage a dhcpv6 on W2008 sp1
i hvae successfully created the prefix and exclusion address, but when i try with a client dhcpv6 do not deliver address, can you help me what are missing ?
Options M and O are set to 1, and the server have a ipv6 address.
Please check is the server has a static IPv6 address bound to the DHCPv6 server.
You can send us the configurations u have made on the DHCPv6 server.