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.
"To configure ISATAP you have to put ISATAP host (A) record in your DNS and all machines can then resolve this name to configure their ISATAP adapters." (Quoted from below article)
Windows Server 2012 Direct Access – Part 1 What’s New
In addition go through beneath articles and thread for more information.
1. Direct Access Windows Server 2012 - ISATAP and Internet connectivity problem
2. 'Real W2orld' Direct Access installation using Windows Server 2012
Hope it helps!
Please do NOT do what Dharmesh suggested. Setting up a DNS record for "ISATAP" is a terrible idea. (sorry Dharmesh, I'm not trying to be hard on you, just the bad information that is out there)
If you have setup a "Selective" ISATAP environment, that is great. It sounds like it is working properly if you are able to successfully RDP into the client machines. This is the correct way to do ISATAP.
For the DNS registration, that is likely a setting in your DNS somewhere that is blocking that from happening. DirectAccess clients will by default register their IPv6 addresses in DNS, so check over the DNS server settings to loosen restrictions there.
For Remote Assistance, Microsoft actually recently released a hotfix to address that not working over DirectAccess - http://support.microsoft.com/kb/2912883/en-us