DirectAccess in ip4 environment

after reading directaccess 2.0 works better in ip4 environment, decided give try.  not working yet, before spending more time troubleshooting or asking specific help, wanted ask general questions see if should be working.

instead of setting pure lab environment, wanted see if work in network setup our production.  of our equipment ip6 capable (modern switches, windows 2008 or higher, clients windows 7).    however, ip6 running default configurations on everything.  in case of our servers, means they're creating own link local addresses , nothing else.  have few switches hosting our pc's.  have a few physical servers, while servers vmware based.  of course, ip4 routable , can communicate else.  ip6 seems limited local broadcast domain.  in other words, 2 workstations on same switch can ping ip6 addresses of each other, not servers on switch.  2 physical servers can ping each other, not vm.  2 vm's can ping each others ip6 address, not 1 of physical servers.

so question is, since ip6 present , enabled everywhere, not configured work, directaccess work?  directaccess smart enough use ip4 translation everything, or try use ip6 server communications, fail?

rich

hi rich,

thanks posting here.

> they're creating own link local addresses , nothing else.

> so question is, since ip6 present , enabled everywhere, not configured work, directaccess work? 

direct access ipv6 base service need ensuring ipv6 has been enabled on internal , external client , server hosts. external clients access internal resources in ipv6 address not in link local addresses under circumstance( nat64 instants). other ipv6 virtual interfaces (isatap or 6to4..etc .) should automatically configured system once enabled ipv6 on hosts.

using ipv6

http://technet.microsoft.com/en-us/library/dd637818(ws.10).aspx

windows 7 directaccess explained

http://technet.microsoft.com/en-us/video/windows-7-directaccess-explained.aspx

> directaccess smart enough use ip4 translation everything, or try use ip6 server communications, fail?

in windows server 2012, da clients smart communicate internal resources in ipv4 proper configuration , can test , experience ourselves following guide below:

test lab guide: demonstrate directaccess simplified setup in ipv4-only test environment in windows server "8" beta

http://www.microsoft.com/en-us/download/details.aspx?id=29029

thanks

tiger li

---

tiger li

technet community support

Windows Server  >  Windows Server 2012 General