You have been very helpful in this post and other posts I see all over.
I know our laptops have IPv6 enabled on our IPv4 network and I am runing
IPv6 enabled on our 2008 r2 domain controller in a lab environment wihtout
issues that I can see. Does it make sense to just leave it enabled with the
link-local IPv6 address(autoconfig)?
"Meinolf Weber [MVP-DS]" wrote:
> Hello 2010,
>
> DirectAccess requires it, that is correct. Also check:
> http://technet.microsoft.com/en-us/n.../dd420463.aspx
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> See here some articles about IPv6 problems:
> http://social.technet.microsoft.com/...1-587e403d58c6
>
> http://support.microsoft.com/?id=952842
>
> http://blogs.technet.com/sbs/archive...-sbs-2008.aspx
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > We have a new installation of a WIndows 2008 R2 domain controller to
> > our IPv4 network. During the installation I noticed IPv6 and IPv4 was
> > installed on the servers main interface. I configured th IPv4 stati
> > settings but leaved the IPv6 settings alone(and enabled). My
> > understanding is that we will need to have IPv6 in order to use some
> > of the R2 features such as DirectAccess however I do not want the IPv6
> > to conflict with our current IPv4 network. Will it ne a problem to
> > leave IPv6 enabled as is the default? Is there information on
> > configuring IPv6 in a IPv4 network?
> >
> > Thanks.
> >
>
>
>