IPv6 router advertisement not configurable on Windows 2008 and 2008 R2 servers.


hello networking experts,

i want configure windows server act publisher ipv6 domain prefix. according article configuring ipv6 windows vista it should easy. if have choosen prefix  fd43:b2bc:bc95::/64 (generated based on computers mac address see http://www.kame.net/~suz/gen-ula.html).

on server configured network this:

netsh interface ipv6 add address interface="local area connection" address=fd43:b2bc:bc95::1  netsh interface ipv6 set interface interface="local area connection" advertise=enabled  netsh interface ipv6 add route prefix=::/0 interface="local area connection" nexthop=:: publish=yes  netsh interface ipv6 add route interface="local area connection" prefix=fd43:b2bc:bc95::/64 publish=yes  

on test machine work pretty well. if try adapt configuration to our domain have problem router advertising remains disabled. tried on domain server (no other role installed) , on other server role installed "network policy , access services" routing , ras running.

if dump configuration following response:

> netsh interface ipv6 dump  # ----------------------------------  # ipv6 configuration  # ----------------------------------    pushd interface ipv6  reset  add route prefix=fd43:b2bc:bc95::/64 interface="local area connection" nexthop=:: publish=yes  add route prefix=::/0 interface="local area connection" nexthop=:: publish=yes  set interface interface="local area connection" forwarding=enabled advertise=enabled nud=enabled routerdiscovery=disabled managedaddress=disabled otherstateful=disabled advertisedefaultroute=enabled  add address interface="local area connection" address=fd43:b2bc:bc95::1  popd    # end of ipv6 configuration    ...     

however  the interface properties is showing following

interface local area connection parameters  ----------------------------------------------  ifluid    : ethernet_5  ifindex    : 11  state    : connected  metric    : 5  link mtu    : 1500 bytes  reachable time   : 26000 ms  base reachable time  : 30000 ms  retransmission interval  : 1000 ms  dad transmits   : 1  site prefix length   : 64  site id    : 1  forwarding    : enabled  advertising   : disabled  neighbor discovery   : enabled  neighbor unreachability detection : enabled  router discovery   : disabled  managed address configuration : disabled  other stateful configuration : disabled  weak host sends   : disabled  weak host receives   : disabled  use automatic metric  : enabled  ignore default routes  : disabled  advertised router lifetime  : 1800 seconds  advertise default route  : enabled  current hop limit   : 0  force arpnd wake patterns : disabled  directed mac wake patterns : disabled  

i tried figure out differences between test machine , designated advertisement server haven't found obvious differences. using procmon didn't either. netsh sets same registry setting on both machines. of course tried playing around other configuration options forwarding, router discovery , on. nothing helped. there must other system parameters prevents server adverting. know reason?

note: having default router advertised or not makes no difference.

btw: if asked question 2 years ago microsoft newsgroup nether got answer. hoped r2 fix there no difference between windows server 2008 , windows server 2008 r2.

any welcome
   ralf

hi, found solution. turned out router discovery must enabled use advertising, try

set int "name" rou=e adv=e

 



Windows Server  >  Platform Networking



Comments

Popular posts from this blog

directory stack

After enabling Windows Server 2012 R2 DHCP Failover Getting Packet dropped because of Client ID hash mismatch

WMI Repository 4GB limit - Win 2003 Ent Question