locked
Cannot manage or ping DA client from internal network RRS feed

  • Question

  • Hi all,

    I have setup a new UAG 2010 SP2 environment and configured Direct Access in a test environment. Clients are connecting over Direct Access just perfect. Internal resources (webmail, file shares) can be used.

    I only have problems managing DA clients from for example SCCM. Internal servers cannot ping the IPv6 address of DA clients. Resolving DA clients IPv6 AAAA record is working. But when pinging the DA client based on hostname or FQDN it cannot find an IP address for the client. When I ping the IPv6 address of the client I get the following error: PING: transmit failed. General failure.

    Within the UAG web monitor the client is succesfully connected over 6to4. The DCA client is in healthy state.

    Hope someone can point me in the right direction.

    Thanks in advance!


    Bart Timmermans | Consultant at inovativ
    Follow me @ My Blog | Linkedin | Twitter

    Please mark as Answer, if my post answers your Question. Vote as Helpful, if it is helpful to you.

    Sunday, January 13, 2013 12:27 AM

Answers

All replies

  • Problem solved :)

    Used the guide from Jason Jones (Microsoft MCS) @ http://blog.msedge.org.uk/2011/11/limiting-isatap-services-to-uag.html

    Remarks (as stated within the comments of his blogpost):

    1. The DNS records must be linked to the internal IP address of your UAG server.


    Bart Timmermans | Consultant at inovativ
    Follow me @ My Blog | Linkedin | Twitter

    Please mark as Answer, if my post answers your Question. Vote as Helpful, if it is helpful to you.



    Sunday, January 13, 2013 1:16 AM
  • What DNS records the self created ISATAP record?

    I have tried that myself and get nothing, once I switch it back to the ISATAP.domain.com I get DNS entries but the transmit failed.

    Friday, June 28, 2013 8:09 PM