I was only referring to the server needing a fixed address not any of the clients. I have always thought that you had to have at least some fixed point to refer to when using DHCP that being the server or more correctly the server's address. Now if we don't need DHCP at all and still get things like DNS for function correctly then we would not need a fixed reference point to work off of.
It is kind of like where in 3 dimensional space is the earth. Do we use the distance from our sun or from the core of the Milky Way as the point of origin. We could use both but then we would need continually be recalculating position for everything to work and distances to be calculated. Using a fixed reference point for objects in space makes it easier to find things without having to recompute angles and distances from fixed objects which would not be fixed unless we had some simple reference points in space to use. Jon On Tue, Jul 13, 2010 at 12:55 AM, Ben Scott <[email protected]> wrote: > On Tue, Jul 13, 2010 at 12:50 AM, Jon Harris <[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. > > > > DHCP v4 needed the same thing as well did it not? > > Sure, but IPv6 isn't IPv4. The whole "stateless address" config > thing means that, in theory, every node can automagically configure > itself with a globally unique IP address without the need for DHCP at > all. If you're a member of that church, DHCP just becomes a method > for nodes to discover things like DNS and mail servers. There's no > reason I'm aware of that should have to be tied to a manually > configured 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/> ~
