Hi, I would like to know whether Windows Seven is able to send a RFC4361 compliant client identifier or not (http://www.ietf.org/rfc/rfc4361.txt). A RFC4361 compliant client identifier is composed of an IAID and a DUID. I would like to use this kind of client identifier in order to have both my DHCPv4 and DHCPv6 clients identified with the same DUID. I tried to set a such client identifier by hand : I added a DhcpClientIdentifier binary value in Regedit which respects the following format : - a byte : type of client identifier => ff - 4 bytes for the IAID - 14 bytes for the DUID (the one generated by the DHCPv6 client). Unfortunately my DHCP server doesn't receive this value, but the following one : 00 ff (4 bytes : IAID) (14 bytes : DUID). What are there two "0" at the beginning ? Thank you in advance. Regards

Yes. Related information is in the following article. DHCP Step-by-Step Guide: Demonstrate DHCP Name Protection in a Test LabArthur Xie - MSFT

Hi, I read this article, but there are things that I don't understand. How can i configure my Windows 7 client to make it send a DUID? My DHCP and DNS services run on a Linux server. This is something that i can't modify. I've just used a network sniffer in my lab, and the client sends only a MAC-address based client identifier. Is that possible to send a DUID without having a AD server and a Miscrosoft DNS and DHCP server. Regards, Thank you!