Quantcast
Channel: Forefront Edge Security – DirectAccess, UAG and IAG フォーラム
Viewing all articles
Browse latest Browse all 1485

Direct Access Configuration Issues

$
0
0

Hi All

We are piloting DA and I just got the servers and DNS entries in place as well as internet facing access to the CRL. I have a laptop that I can get the HTTPS tunnel setup (we are planning on using this for production none of the other technologies). I have the "DirectAccess Client Troubleshooting Tool" from Microsoft and have been using it to try to identify issues. In the "Interface Test" everything is green. Under "Network Location Test" the DNS server address that it is trying to connect to is the IPV6 address of the DA server internally. I can't get it to display anything but the IPv6 address during setup under "Remote Access Server" the interface shows the same IPv6 address. I don't think that's how it's supposed to work, but I can't seem to stop it from doing that either. 

In EVERY example I can find of setting this up as a "behind an edge device with single adapter" the screenshots show the IPv4 address of the server, not the IPv6 address. I think this is the problem, but turning off the IPv6 on the adapter prevents me from completing any part of the setup wizards.

Anyone else run into this? How did you fix it?


Allen George - MCSE: Server Infrastructure


Viewing all articles
Browse latest Browse all 1485

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>