Posts tagged: Networking

Tip about setting up Static IPv6 address for Domain Controllers

This is a slightly random/out of context blog post as it’s not really related to Exchange or OCS, however for those setting up lab systems or actually, any network where a domain controller is being built this might be of use.

I have never really looked into the correct settings for IPv6 on a DC and have therefore often have warnings about not having a Static IPv6 address.

Well whilst rooting around the TechNet site trying to work out how to setup an AD RMS install, I found a step by step guide to setting up a lab – http://technet.microsoft.com/en-us/library/cc753531%28WS.10%29.aspx

One snippet that caught my attention was how IP addresses should be configured on a Server 2008 (or 2008 R2) domain controller.

Configure TCP/IP properties so that the domain controller has a IPv4 static IP address of 10.0.0.1 and a IPv6 static IP address of FEC0:0:0:1::

I also found these steps which seems to suggest disabling IPv6 which I know from various posts has the potential to cause issues as Windows 7 and Server 2008 R2 expect to use it for internal communications.

To configure TCP/IP properties

  1. Log on to the domain controller with an Administrator account.
  2. Click Start, click Control Panel, click Network and Internet, click Network and Sharing Center, click Manage Network Connections (or Change adaptor settings on Server 2008 R2), right-click Local Area Connection, and then click Properties.
  3. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
  4. Click the Use the following IP address option. In the IP address box, type 10.0.0.1. In the Subnet mask box, type 255.255.255.0, and then click OK.
  5. On the Networking tab, clear the Internet Protocol Version 6 (TCP/IPv6) check box, and then click OK.
  6. Click OK to close the Local Area Connection Properties dialog box.

So I did a bit of reading around and asked a few colleagues and came up with a few nuggets.

In IPv4 we mostly use private subnets (10.0.0.0/8, 172.16.0.0/16 and 192.168.0.0/16) for internal networks. In IPv6, the equivalent type of address is a Unique Local Address (ULA or link local) for use in the local network. This is an absolutely massive range of addresses which it is basically impossible to use up!

However, the key thing is that Windows Server 2008 R2 only considers Global Unicast IPv6 as an equivalent for “static” IPv4 addresses. Unique Local Addresses (FC00::/7) are not “static” IP addresses.

So what we need to do is assign a Global Unicast address to the server to stop us being prompted that a Static IP in not set.

I also found a bunch of resources which might help get people started in IPv6

Chapter 3 of the TCP/IP Fundamentals for Windows– IP Addressing:

http://technet.microsoft.com/en-us/library/bb726995.aspx

Wikipedia – For a load more info about IPv6 see here:

http://en.wikipedia.org/wiki/IPv6#Special_addresses)

You can use this calculator to get the correct IPv6 addresses for your needs:
http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php

This is a TechNet magazine article:

http://technet.microsoft.com/en-us/magazine/2007.08.cableguy.aspx

And finally this work by Joe Davies comes highly recommended from my friend and Directory Services MVP Laura E. Hunter

http://blogs.msdn.com/joe_davies/archive/2008/02/11/the-windows-server-2008-networking-suite-published.aspx

 

And at the end of this what conclusion did I come to?

Basically at the moment unless you need to use IPv6 in your network (which I acknowledge that many US Public organisations do) don’t worry about it! You will get an occasional message but essentially IPv6 is clever enough to sort itself out in the majority of cases!

Happy reading!

Cheers

Nathan

WordPress Themes

Get Adobe Flash player