This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

DirectAccess 2012 and IPv6

Question
0

Sign in to vote

I have a quick question for those who know, is the traffic between a DA client and the DirectAccess server still IPv6 like it is in UAG 2010? Reason is that the Lync app is not IPv6 aware and forced tunneling breaks it in UAG 2010 but if 2012 uses IPv4 then the Lync app should work.

Thursday, November 22, 2012 4:54 PM

Answers

0

Sign in to vote
Hi,

Thank you for the post.

Windows server 2012 direct access server has built-in NAT64 and DNS64 support for accessing IPv4-only resources.

Regards,
Nick Gu - MSFT
- Proposed as answer by Nick Gu - MSFTModerator Thursday, November 29, 2012 2:14 AM
- Marked as answer by Yan Li_Microsoft community contributor, Moderator Thursday, December 6, 2012 8:54 AM
Wednesday, November 28, 2012 6:40 AM

Moderator

All replies

0

Sign in to vote
Hi,

Thank you for the post.

Windows server 2012 direct access server has built-in NAT64 and DNS64 support for accessing IPv4-only resources.

Regards,
Nick Gu - MSFT
- Proposed as answer by Nick Gu - MSFTModerator Thursday, November 29, 2012 2:14 AM
- Marked as answer by Yan Li_Microsoft community contributor, Moderator Thursday, December 6, 2012 8:54 AM
Wednesday, November 28, 2012 6:40 AM

Moderator
0

Sign in to vote

Hi,

In regard to traffic between the client and the DA server it is still IPv6 like with the UAG.

A suggestion is that you exclude the Lync DNS records in your NRPT rules and have your DA clients connect to the edge server like an external client would.

One Place you could read to see what to exclude is http://donnystyle.wordpress.com/2011/04/17/configuring-directaccess-for-lync-ocs-voicevideo-in-a-split-dns-scenario/

Jonas Blom | Relevo AB | http://blog.nrpt.se

Thursday, November 29, 2012 3:19 PM