My contribution to IPv6 day will be this small “lab” test where I will show you some basic IPv6 configuration that you can do with Windows server 2008 R2.
Here are the videos:
IPv6 day – configuring IPv6 in Windows server 2008 R2 part 1 - http://www.screencast.com/t/Ifj2lx4hTG
IPv6 day – configuring IPv6 in Windows server 2008 R2 part 2 – http://www.screencast.com/t/PSf3q5yr4BF
What do we have in our LAB?
1. Windows server 2008 R2 with two network cards:
External – with IPv6, gateway and DNS configured
Internal – with IPv6 address only
External IP has internal class static routed on our Cisco router in front of Windows server external card.
2. Windows 7 machine with single network card that is connected to the same switch as servers’ internal card.
What will we do:
In the fist video:
First we will start with some basic checking of network configuration on server.
Then we will run netsh (I run a command prompt with “Run as administrator”) and go to
netsh / interface / ipv6
show route we can see ipv6 routes currently configured – we would like to enable publishing of route that I have highlighted in the video.
set route PREFIX INTERFACE_NUMBER publish=yes
then we will run an command to enable advertising, to disable address management (so Windows 7 will generate IPv6 without help od DHCPv6) (M flag) and we will disable other stateful configuration (O flag).
set interface INTERFACE_NUMBER adv=enabled managed=disabled other=disabled
Meanwhile we are checking IPv6 connectivity from our Windows 7 machine… Windows 7 is still unable to ping outside the network…
well we need to configure some other stuff on server now… we will enable forwarding on our two interfaces (External and Internal)
set interface INTERFACE_NUMBER forwarding=enabled
still no connectivity from win 7?
last step that we need to do on our server is to advertise default route to our clients…
set interface INTERFACE_NUMBER advertisedefaultroute=enabled
So our Windows 7 sudenly start to recive ICMPv6 echo replyes from some IPv6 machine outside our network WUHU!
But Windows 7 machine is not able to resolve hostnames to IPV6 addresses – this is becouse we have now global IPv6 address configured and default gateway – so we have connectivity but we are not able to resolve hostnames as we do not have any DNS servers to do that.
On Windows server 2008 R2 I will start the installation of two roles – first DHCP role which I wil configure later and DNS role.
When the roles are installed I will configure so called forwarders on my DNS server so my clients will be able to use my server as a DNS server for their queries.
In the second video:
I will first flush IPv6 configuration on Windows 7 machine by using command
ipconfig /renew6 (is the opposite command to regain IPv6 configuration)
Secondly I will configure DHCPv6 server by starting New Scope wizard under IPv6 settings…
I will configure prefix – this ipv6 prefix of Internal network card
Skip the exceptions and activate the scope…
You will see that Windows 7 still did not ask DHCPv6 servers for address this is becouse managed flag is set to disabled on server so…
in netsh / interface / ipv6 we need to activate managed flag by inserting this command:
set interface INTERFACE_NUMBER managed=enabled
Our Windows 7 machine can now be found in IPv6 leases on our DHCP server – but still it is unable to ping hostnames on the internet… This is becouse our DHCPv6 server is not giving DNS servers as scope options and Other stateful flag is disabled.
So we first need to add DNS Recursive Names Server IPv6 Address in our Scope options and then use netsh command:
set interface INTERFACE_NUMBER other=enabled
Yeeepppeee!!! Our Windows 7 is ready to ping hostnames on the internet – so it is able to surf the IPV6 internet…
When I am finishing this article is 8.6.2011 23:37 – this is my small contribution to IPv6 day so happy IPv6 day to all of you!