Identify non-ipv6 aware applications for Direct Access

Hi all,

we are in process of implementing direct access using windows server 2012 r2. As we all are aware that applications which are not ipv6 aware does not work over DA tunnel.

what is the best way to identify whether an application is ipv6 aware because when an application does not work over DA there could be other reasons for it.  how we can be 100% sure about compatibility of applications with ipv6?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
Applications normally don't care about the ip address scheme an application works at a much higher level of the tcpip stack. Any application that uses fixed ip addresses will not work over Direct Access i.e. \\\share\filename.ext will not work since you may or may not have access to that internal ip address. but\sharename\filename.ext will work since it uses a public ip address the ip stack will handle this and use the correct version of the ip protocol.
shubham87Author Commented:
Hi David,

Thanks for your reply. As per my understanding, application need to have support for IPv6 stack in order to be able to work over DA. One example is, Lync 2010 which does not work over DA and it is well documented that Lync 2010 do not have IPv6 support. Since Lync 2010 is very well known application and it is easy to get information on which is not the case with other applications. Hence my original question was, if we have some other way to identify whether or not application has been built with IPv6 stack support.

Also,\sharename\filename.ext will not work over DA tunnel, since in DA everything has to be accessed with a DNS name since its NRPT table which decides which DNS server to be used with which domain.

Once again, thanks again for your time.

David Johnson, CD, MVPOwnerCommented:
you don't need direct access for lync for users connecting via the WAN just need an edge server .. nor do you need direct access for Outlook to your on prem exchange. But for other network resources read file's the application doesn't care neither does SQL server. All direct access does is eliminate the need for a vpn from the client to the server.
shubham87Author Commented:
I have been able to identify one simple way to identify. Applications which do not support IPv6 bind themselves to IPv4 address while trying to communicate and you could actually figure that out in netstat or using a packet capture.

This may not be the perfect solution, but has worked for me.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
shubham87Author Commented:
Found a work around myself
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.