Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Adding IPv6 to Windows 2008/7 domain

Unanswered Adding IPv6 to Windows 2008/7 domain

  • Thursday, February 14, 2013 4:17 PM
     
     
    Sign In to Vote
    0

    I currently have a simple Server 2008/Windows 7 network that uses IPv4. Our core network infrastructure did not support IPv6 so I disabled it on the servers but left it enabled on the Windows 7 machines. Windows 7 computers can only see other Windows 7 computers on their own subnet using Link Local addresses which I suspect is intended. Now that my L3 switches can see(switch) IPv6 what do I need to do to run IPv6 and IPv4 in a double-stack environment? From what I have read it sounds like a Link Local address is a unique address but is it considered a static address? Generally DHCP, DNS, etc servers need static addresses. Do I need to assign specific addresses to clients via IPv6 DHCP or are Link Local addresses sufficient? Do I need to turn off the Mac masquerade feature on the servers so they have a "real" address? I added the reverse lookup zone for FE80:: to DNS. When I turn on IPv6 on the AD/DNS servers do I have to manually set DNS to listen on the IPv6 address or does it do that automatically?

    Thx in advance

    eburch@lasertel.com

     

All Replies

  • Wednesday, February 20, 2013 10:12 AM
     
     
    Sign In to Vote
    1

    Hi

    1. LinkLocal address are only valid in the subnet (unrouted).

    2. Static address can be assigned manualy or by dhcpv6

    3. First make ipv6 Addressing scheme (ULA or provider assigned prefix) after that you can bring up ipv6. Otherweise may you get stuck.

    4. Disable any Tunnels (DisabledComponents 20)

    5. Setup a isolated Lab (in hyper-v ?) and test test test. 

    ipv6 is tricky but fun

    steini

     
  • Wednesday, February 20, 2013 3:33 PM
     
     
    Sign In to Vote
    0

    I thought the autoconfiguration link local addresses function like a subnet if the switch passes IPv6 traffic? I can configure the core switch with an autoconfiguration link local addresses or a static address. If the address is static then the switch routes (layer3). Is there a reason not to use a site-local unicast address scheme other than it is viewed as deprecated? Our provider hasn't addreesed global unicast addresses yet as far as I know. SLU allows NAT to the net. I assume either way picking the subnet is similar to the process one picks a subnet with IPv4 privates addresses.

    Thx

    eburch@lasertel.com

     
  • Wednesday, February 20, 2013 11:43 PM
     
     
    Sign In to Vote
    0
    I have been reading a bit more since this mornings post. How is the random part of the unique local address set? I know the address starts with FD00:: but I am not sure how the next 40 "random" digits get set. Is there a tool or will any random number generator work? Also, do I disbale all the translation (6to4,Teredo,usatap,etc) on all interfaces. From what I understand my L3 switch "routes" IPv4 traffic but "switches" Ipv6 traffic. Wouldn't that make all nodes on the network a single subnet? I only have 170 nodes so it isn't big by network standards. I subnetted it long ago when the infrastructure was all hubs.

    eburch@lasertel.com

     
  • Sunday, March 03, 2013 11:25 AM
     
     
    Sign In to Vote
    1

    Hi EBurch,

    FD00:: -> ULA http://en.wikipedia.org/wiki/Unique_local_address -> yes comparable with ipv4 Private Ranges.

    Some nice IPv6 Facts
    http://singapore41.icann.org/meetings/singapore2011/presentation-cira-ipv6-experience-latour-20jun11-en.pdf
    (says do not use ULA - i could not figure out why)

    ULA generator
    http://www.simpledns.com/private-ipv6.aspx

    L3 Switch
    i do not understand - maybee an old piece ? ->check hw support or with wireshark
    http://en.wikipedia.org/wiki/Multilayer_switch#MultiLayer_Switch_.28MLS.29_-_OSI_layer_3_and.2For_4
    L2 = arp(VLAN) / L3 = ipAddresses(Router)

    An this point i'm also unsure about the perfect IPv6 implementation in a Windows environment. My Playground is still under construction.
    According to the cira document, i dont know whats better about the addressing scheme (Tunnelbroker Range or ULA).
    But for production systems i recomend no Tunnels and IPv4 Priority (Today).

    steini 

     
  • Monday, March 04, 2013 2:55 PM
     
     
    Sign In to Vote
    0

    Steini

    Thanks for all the help. The generator is very helpful. I will start testing in the sandbox and see what happens. It looks like all the translation methods should be disabled and can be with group policy. Definitely different. Some of MS products still need IPv4 so "mixed IP" seems to be the rule for now.

    Thx again

    eburch@lasertel.com

     
  • Thursday, April 18, 2013 9:20 AM
     
     
    Sign In to Vote
    0
    Hi Steini,yes are correct autoconfiguration link local addresses  FE80 is unrouted and valid to subunits on the subnet and my question is,since you mentioned testing Ipv6 on an isolated lab in (Hyper-V)...Have you been able to Setup a testlab on Ipv6 if so can you please direct me on steps on how to set one up.... I appreciate that.