Windows Server 2008 is Generating Erroneous DHCPv6 Solicit Packets


greetings.

i have windows server 2008 machine 2 ethernet interfaces. internal interface has static local area network address , works ipv4 only. second interface external, gets class-based ipv4 through provider's dhcp server , bound perform stateful autoconfiguration (in order obtain ipv6 address).

typically dhcpv6 client unable request ipv6 address. @ point during os boot able address, still unable renew lease afterwards.

careful analysis of ipv6 traffic has shown solicit messages external interface incorrect. "client information" extension contains mac-address of other, internal interface, in no way related external interface. provider's dhcpv6 correctly replies advertise message, silently discarded due mac-address mismatch.

i appreciate or further information on case, i'm out of options.

the dhcpv6 client , running. still, mac-address in "client information" extension stays incorrect. thus, seems address there has no effect on protocol implementation.


Windows Server  >  IPAM, DHCP, DNS



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client