| T O P I C R E V I E W |
| St0ne_c0ld_316 |
Posted - 05/31/2012 : 1:38:33 PM
We are running Windows 2008 R2 and Windows 2003 on our DC's.
A mix of Windows 2000-2008r2 servers, Windows NT-7 workstations.
All of our route switch environment is able to but not configured for IPv6 routing of any kind.
We don't have any hard coded IPv6 internally.
Should we hard code IPv6 and create AD Sites?
Should we change the precedence of IPv6 and lower it?
Any documentation would be really cool. |
| 6 L A T E S T R E P L I E S (Newest First) |
| St0ne_c0ld_316 |
Posted - 05/31/2012 : 5:34:54 PM
Yep, In DNS you need to register IPv6 as AAAA
I'm just getting up to speed on IPv6 - noone else will :) |
| Curt |
Posted - 05/31/2012 : 5:29:13 PM
I ran into a bit of problems with ODBC errors with resulting 18456 SQL errors on a large WAN.
Seems like the IPV6 A records in the DNS forward lookup zone could not use it.
|
| wobble_wobble |
Posted - 05/31/2012 : 5:11:58 PM
by default 2008 and 2008R2, where they see IPv6 addresses and have discovered other IPv6 addresses they will use IPv6 to ping. You probably have to use ping -4 192.168.1.X to ping a device from these "troublesome" servers.
Technically they can talk to each other using neighbour advertisements.
You should be able to ping them, using the IPv6 address:linklocalID
You can disable IPv6 networking on the NIC's and see what happens....but in a live environment, be aware of the potential for bad stuff to work, so build a test server or 2 and go from there.
If you have specific errors, post them, we'll see what we can do.
|
| St0ne_c0ld_316 |
Posted - 05/31/2012 : 4:55:15 PM
lol - obviously it IS broken or I wouldn't be posting!
The links look good - I'll take a look at those - thank you.
What we are seeing is that Windows 2008 devices are able to talk to Windows 2008 R2 DC's and will obviously use IPv6. As there are no IPv6 sites in AD there are errors about IP addresses not mapping to those in the environment etc. No ACTUAL errors yet, but I don't really want to wait and see if there are any before we start remedial action! |
| Curt |
Posted - 05/31/2012 : 4:35:36 PM
I second Joe's advice.
There is quite a bit of equipment out there that is not ready for IPV6 yet and the coin is not going to be there for a while to replace it all.
Add to that the odd things that happen with virtual NICS on virtual servers and you have some real bleeding edge stuff to handle.
If you like the challenge then go for it but not on another company's dime.
quote:
Originally posted by wobble_wobble
Best advice - if it ain't broke, don't fix it.
Second piece of advice - http://technet.microsoft.com/en-us/library/gg250710(v=ws.10).aspx
http://url.ie/fdpb
Third - Nathan
http://nathanwinters.co.uk/2010/04/08/tip-about-setting-up-static-ipv6-address-for-domain-controllers/
IPv6 needs DNS to work well and for the routing to be IPv6 configured.
It works, but weird can happen and not all the weird is known yet, so do it in a test lab first.
For other stuff, check out here
http://www.worldipv6day.org/
http://www.worldipv6launch.org/
|
| wobble_wobble |
Posted - 05/31/2012 : 4:05:38 PM
Best advice - if it ain't broke, don't fix it.
Second piece of advice - http://technet.microsoft.com/en-us/library/gg250710(v=ws.10).aspx
http://url.ie/fdpb
Third - Nathan
http://nathanwinters.co.uk/2010/04/08/tip-about-setting-up-static-ipv6-address-for-domain-controllers/
IPv6 needs DNS to work well and for the routing to be IPv6 configured.
It works, but weird can happen and not all the weird is known yet, so do it in a test lab first.
For other stuff, check out here
http://www.worldipv6day.org/
http://www.worldipv6launch.org/
|
