locked
Direct Access client connectivity RRS feed

  • Question

  • Hello
      We have set up direct access for our client to test but we are stuck with the following issue:

    While the client connects through direct access ip-https (disabled 6to4 and teredo and checked httpsinterface with netsh) and can access internal resources the remote client status console shows no connections.

    Have checked the Iphlpsvc log and get this:

    IP-HTTPS client Unknown (x.y.z.28) is associated with IP address (ipv6 address)

    The base filtering engine flow and connection logs are empty.

    Any Ideas????

    Thank you,

    • Edited by voutman Monday, July 25, 2016 9:33 AM
    Monday, July 25, 2016 9:25 AM

Answers

  • Hi voutman,

    >While the client connects through direct access ip-https (disabled 6to4 and teredo and checked httpsinterface with netsh) and can access internal resources the remote client status console shows no connections.

    Please check the following things:

    1. On DA client, check if it could access the Internet, open an IE and ensure you can access Internet locations;

    2. Please post an ipconfig/all on the DA client. If IP-HTTPS is being used, there should be an IPv6 address assigned;

    3. Use netsh interface httpstunnel show interfaces to display the IP-HTTPS URL, also ping the FQDN in the URL to check if the DA client could resolve the name of the IP-HTTPS server in the URL and reach the resolved IPv4 address of the DA server.

    4. Also check if you can access the above URL via IE to check if there are certificate errors.

    Best Regards,

    Anne 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Tuesday, July 26, 2016 7:09 AM