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

windows 2012 direct access iphttps site

$
0
0

I've setup direct access on windows 2012, single NIC behind NAT device topology.

We have a thirdparty ssl cert, which has been used during the setup wizard. internal pki for computer

and server authentication certs, plus a external dns name for the internal server port 80 and 443 forwarded through our firewall.

When I browse to the site via domain name either internally or externally I get the IIS 8 landing page. When I try and enter

https://fqdn:443/IPHTTPS either internally from the server itself, LAN computer, or externally via a client computer I get nothing

no response. If I use the internal ip from the server itself or from a LAN computer I get a certificate error, and then an error 404 page not found. the cRL for the third party ssl cert if accessible, and my understanding is there's no specific changes you need to make to bindings in IIS on the direct access server. Any ideas of what results I should be seeing. 


Viewing all articles
Browse latest Browse all 1485

Trending Articles



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