I need to assign a static address to the server. As far as I can tell, that is against SLAAC, and everything else IPv6 is supposed to make easy. There might be a reason. I haven't uncovered it.
-----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Monday, July 12, 2010 10:29 PM To: NT System Admin Issues Subject: Re: DHCPv6 No familiarity with DHCPv6, so an ignorant question... What needs the static address assigned? Is it the machine handing out addresses, or the machine receiving the assignment? And, if the former, why would that be an issue? I would think it pretty much a requirement. I *did* just go to a computer user group in Seattle that had a presentation on IPv6, but aside from the fact that it allows for more addresses than we can count, and a few other tidbits like getting started with tunneling, it wasn't all that informative. For instance, he did not deal with issues like whether segmenting networks as we do now inside the enterprise at the layer2 and layer3 boundaries is still an issue in a pure IPv6 environment - I think that was beyond his experience. Kurt On Mon, Jul 12, 2010 at 19:18, Jason Gauthier <[email protected]> wrote: > Well, after diligence and testing… I’ve solved this. Windows 2008 > DHPCv6 will not work reliably without having a static IPv6 address assigned > to it. > > I have not decided how I feel about that yet. > > > > From: Jason Gauthier > Sent: Friday, July 09, 2010 3:12 PM > To: NT System Admin Issues > Subject: DHCPv6 > > > > Greetings, > > > > I’m struggling with an issue with DHCPv6. I’m using this, > effectively, as stateless. I have a Cisco router set up to multicast > router advertisements. It is doing so successfully, setting the options > “Managed” > to false, and “Other” to true. > > > > I have confirmed through network traces and Windows 7 DHCPv6 event > logs that it is receiving the announcements, and setting the options > correctly. > > > > This is working good! > > > > Now, here comes the part that I’m struggling with. Once the options > are set, the client machine should (and does) poll for DHCPv6 options only. > > Again, I’ve confirmed though network traces that this is happening > successfully. > > > > 15:03:45.012474 IP6 (hlim 1, next-header UDP (17) payload length: 110) > fe80::188b:8ff9:305c:71a3.546 > ff02::1:2.547: [udp sum ok] dhcp6 > solicit > (xid=fd9725 (elapsed time 3100) (client ID hwaddr/time type 1 time > 316484303 > 00155d320606) (IA_NA IAID:369104221 T1:0 T2:0) (Client FQDN) (vendor > class) (option request DNS name DNS vendor-specific info Client FQDN). > > > > My DHPCv6 server (running netmon) can definitely see the multicast > requests sent to FF02:0:0:0:0:0:2:1. However, it doesn’t respond, > acknowledge, or otherwise seem to care. > > > > Options 23 (DNS Recursive Name) and options 24 (Domain Search List) > are set. > > > > I have done this on two different networks, two different DHCPv6 servers. > Neither of them responds. Even the statistics do not count up that > there was a solicit message. > > > > I am intending to open a ticket with MS, but sasupport seems to be > non-functional for me at the moment. > > > > So, I thought I would ask here. All my clients are Windows 7/2008R2, > and my two servers are 2008 R2. > > > > Thanks for reading. > > > > Jason > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
