I'm going to test this out again this week (hopefully). I did all of this back in December, but I don't remember if I actually had to set a static IPv6 address before my DHCP server started working, or if I manually set it because I wanted to control the range of addresses.
-ASB: http://XeeSM.com/AndrewBaker On Tue, Jul 13, 2010 at 10:21 AM, Ben Scott <[email protected]> wrote: > On Tue, Jul 13, 2010 at 7:57 AM, Jason Gauthier <[email protected]> > wrote: > > 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. > > Going with "path of lease resistance" as human nature, I would > speculate that one possible reason the MS DHCP server wants a static > IPv6 address is because it's based on the DHCPv4 code which assumes a > static IP address. > > -- Ben > > ~ 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/> ~
