none
Assistance troubleshooting apps not working over Direct Access/UAG RRS feed

  • Question

  • Where to find MS partner/integrator able to assist with troublehsooting various apps we have that will not work over direct access. Any recommendations (US)?
    Wednesday, June 9, 2010 10:45 PM

Answers

All replies

  • Out of curiosity, what problems are you having and which apps?
    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk
    Wednesday, June 9, 2010 10:57 PM
    Moderator
  • Hi,

      Please contact me directly at noamb@microsoft.com

    Regards,

    Noam

    Thursday, June 10, 2010 10:27 AM
  • Thanks for the response …

     

     

    We run JDEdwards on an as/400.

    We use a terminal emulator application on the Win7 deskktops called ClientAccess that does connect successfully to JDE over Direct Access.

    We also have an application called Showcase Strategy that is a reporting tool that will NOT connect over Direct Access.

    The vendor does not support Showcase on Windows7 anyway but it does run on a Win7 laptop on the LAN or over a VPN .. just not over Direct Access.

    It uses a custom ODBC connector that doesn’t offer much insight into why it won’t work.

     

    I was hoping to get a walk through on troubleshooting something like this .. where is it failing and is there anything we can do to coax it to work.

     

    Another application is the Avaya Softphone v R6.01.93 …  Again it is not supported on Win7 anyway so vendor won’t help .. but it does work on Win7 over a regular VPN .. but will not connect over Direct Access.

    Thursday, June 10, 2010 9:42 PM
  • "All communications between the DA client and server are over IPv6. What this means in practice is that the client application must be IPv6 aware. This is not to say that the server side of the application needs to be IPv6 aware and in most cases the server side will work fine with the help of the UAG NAT64/DNS64 IPv6 protocol translator if the server side is only IPv4 aware – but the client side must always be IPv6 capable."

    Source: http://blogs.technet.com/b/tomshinder/archive/2010/03/30/more-on-directaccess-split-tunneling-and-force-tunneling.aspx

    I am guessing (like Citrix and OCS) that your applications are not IPv6 aware...

    Cheers

    JJ


    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk
    • Marked as answer by Erez Benari Wednesday, June 16, 2010 11:47 PM
    Friday, June 11, 2010 8:19 AM
    Moderator
  • Was a solution ever found? I'm facing the same issue using DirectAccess 2012 trying to connect to a HP3000 with a terminal emulator.

    Thanks ~Mike


    Mike Pietrorazio

    Monday, August 5, 2013 6:24 PM
  • In the case where an application is trying to communicate with an IPv4 address directly (like most softphone applications), this is never going to work over DirectAccess. All DA traffic must be IPv6 and talking directly to IPv4 addresses just isn't going to happen.

    In the more common case where an application is trying to talk to a name which resolves to IPv6 correctly over DA, but the app still doesn't work, like Jason said this generally means that the app was coded in a way that it doesn't know how to generate IPv6 packets. The company that I work for has a utility that corrects this behavior, at least for many of the apps we have thrown at it. Check it out here if you are ever interested: http://www.ivonetworks.com/news/2013/05/ivo-networks-announces-app46-for-directaccess/

    Tuesday, August 6, 2013 1:11 PM