Windows Server - Publish Exchange OWA with SSL in TMG

Asked By Floris Verstegen

14-Jun-10 06:02 AM

I cannot get Forefront TMG to create an HTTPS listener that uses form based
authentication for publishing Microsoft Exchange Outlook Web App 2010.

Forefront is running on Windows Server 2008 R2 64 Bit Enterprise Edition.
The machine is member of the domain and I use a wildcard certificate from my
own domain certificate service. The certificate is imported into the Personal
store of the Computer and appears as a valid selectable certificate in TMG.
When I publish OWA 2010 with a Web Listener I select the certificate and
select form based authentication. When browsing to my public IP Address from
a remote system I get a page cannot be displayed error from Internet Explorer.
In the logging on Forefront I do see two entries indicating a connection
attempt from the remote system:

Initiated Connection SVTMG01 6/13/2010 12:16:50 PM
Log type: Firewall service
Status: The operation completed successfully.
Source: External (xxx.xxx.xxx.xxx:2304)
Destination: Local Host (xxx.xxx.xxx.xxx:443)
Protocol: HTTPS

Additional information
Number of bytes sent: 0 Number of bytes received: 0
Processing time: 0ms Original Client IP: xxx.xxx.xxx.xxx

Closed Connection SVTMG01 6/13/2010 12:16:50 PM
Log type: Firewall service
Status: A connection was gracefully closed in an orderly shutdown process
with a three-way FIN-initiated handshake.
Source: External (xxx.xxx.xxx.xxx:2304)
Destination: Local Host (xxx.xxx.xxx.xxx:443)
Protocol: HTTPS

Additional information
Number of bytes sent: 584 Number of bytes received: 4367
Processing time: 0ms Original Client IP: xxx.xxx.xxx.xxx

I can get this to work fine when using HTTP, but not with HTTPS and a
certificate. I already did a reinstall of the entire machine, tried a
different port for HTTPS and a non wild-card certificate.

14-Jun-10 10:55 AM

Does that mean you are using the IP#?  You cannot do that,...you have to use
the actual correct FQDN.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

14-Jun-10 01:15 PM

@Phillip Windell

No I am using the FQDN with the configured subdomain. I just wanted to point
out that I do connect to the machine on it is public network interface.