|
Posted by =?Utf-8?B?U09GVUxMRVI=?= on March 28, 2006, 4:31 pm
If you were Registered and logged in, you could reply and use other advanced thread options
The solution in our case was to create a certificate using Windows 2003 CA,
install the certificate on IIS (Changed default web site SSL port from 443 to
444) on the ISA2004.
Reconfigure the Firewall redirect rule to use HTTPS/SSL only and reference
the certificate created. This provides Secure TSAC Internet access to the
ISA2004 and then the traffic is redirected HTTP to the Terminal Server
cluster as it was before.
--
Scott
"SOFULLER" wrote:
> We have 2-load balanced Terminal Severs on our Intranet called TERMSRV1 and
> TERMSRV2. We want to enable SSL on both for employee access via the Internet.
> The Intranet NLB Cluster Name is TERMSRV and the FQDN on the Internet is
> TERMSRV. We redirect HTTP requests for TERMSRV from the Internet to the
> Intranet FQDN/NLB Cluster name TERMSRV via redirection using ISA2004 and can
> do the same for HTTPS.
>
> Would the certificates for both TERMSRV1 IIS and TERMSRV2 IIS be unique to
> each server's FQDN or the NLB FQDN CLuster Name?
>
> Thanks,
> scott
>
>
> --
> Scott
| 
XML site map