Cannot manage or ping DA client from internal network

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 ad

January 13th, 2013 3:27am

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.

Free Windows Admin Tool Kit Click here and download it now
January 13th, 2013 4:16am

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.

June 28th, 2013 11:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics