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

Public and Private IP with same DNS causing Direct Access Error?

$
0
0

I'm having trouble getting through the Direct Access wizard.  It gets to "Updating Network Connectivity Assistant settings" and dies with the error "No such host is known."  It'd be nice if it gave a few more details on what host it's talking about but I was wondering if maybe it might be because our Internet facing NIC's IP address and the public IP that it's NAT-ed to have the same name in DNS but they point to different IP addresses depending on whether you're trying to resolve it from the Internet or from the private side of the network.  (For example if I were to ping daserver.mydomain.com from inside I'd get the private IP 10.0.0.10 and if I would ping it from a box that is on the Internet I get a public IP like 164.123.145.160.) 

I've tried entering just the public IP of the DA server and the DNS name into the "Type the public name or IPv4 address used by clients..." field of the wizard and the result is the same.  I also installed KB2929930 and the only difference I noticed is that the public IP is entered in the wizard by default now.

This is a Server 2012 R2 dual NIC DA installation behind a NAT and an edge firewall with only port 443 open to the Internet.


Viewing all articles
Browse latest Browse all 1485

Trending Articles



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