Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How do I configure stateful DHCPv6 in Windows Server to allow clients to ping each other?

I would like to configure my Windows 2k8 DHCP server to distribute IPv6 addresses in my office network that does not have an IPv6 compatible router. I'll be using ULA, FD01::/64

I have been able to configure the clients to receive addresses from the server, however they are not able to ping each other.

After some research, I've learned that their routing tables are missing a necessary route to the local network. (/64)

What is the best way to fix this? The only thing I've seen to far is to add the route via command line on each client. That doesn't seem like a practical solution. If corporations are using stateful vs stateless mode, there must be a way around this.

share|improve this question
Setup your Windows server as if it was an IPv6 router perhaps? I believe it can do that. – Zoredache Apr 12 '13 at 0:27
out of curiosity why are you using ULAs for what sounds like a production network? If you really need a ULA I would recommend you use a generator like – Jim B Apr 12 '13 at 4:27
Are you also sending out router advertisements? you still must announce the prefix with an RA - disable the autonomous flag if you don't want hosts to do SLAAC. – Olipro Apr 17 '13 at 9:20
Is that the answer? RAs are always required? Is a Windows server able to send RAs? – Corey Apr 18 '13 at 13:43
Yes, RA's are always required. An RA is how a client knows it's supposed to DHCPv6 instead of doing SLAAC. – fukawi2 Apr 29 '13 at 6:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.