I have DirectAccess configured on Server 2012. Just a single NIC configuration. I've got it configured to work with Windows 7 and everything is fine as far as accessing network resources from the DirectAccess client, but not the other way around.  I've setup ISATAP for the machines that I want to communicate with the clients and that appears to be working.

The first problem we are having is the client will not register with our DNS servers. 

If we manually add a record with it's IPv6 address, we can ping the client, RDP to the client, but Microsoft Remote Assistance or trying to browse to the client doesn't work. 

I believe I have opened the correct ports and allowed edge traversal on the client. Do you guys have any other suggestions? Thank you.

Hi

Tricky problem. If you can ping your DirectAccess clients from LAN and perform RDP, it's not a DirectAccess problem but a Windows Remote Assistance. There are some rules in the incoming firewall node that must be enabled and configured for edge transversal, you're right.

Let's see if it's a Windows Remote assistance bug fixed recently with the following KB : http://support.microsoft.com/kb/2912883. It's for Windows 7 and seems to fit to your scenario.