Certificate error on Outlook 2007 clients

[Hoof Hearted]

When a client pc is configured to use Wingate as a proxy server, and then opens Outlook 2007, a certificate error is displayed. The error states that the name on the certificate does not match the name of the site.

If I then configure that client not to use a proxy server, the certificate error goes away.

Is this a known problem?

Ian

[adrien]

Hi

what is outlook trying to connect to? What activity shows up in GateKeeper when this happens?

Are you intercepting secure POP to some service in WinGate with SSL on the binding?

Adrien

[Hoof Hearted]

Outlook is trying to connect to autodiscover.ourdomain.co.uk It manages to do this, but it always throws up the certificate error when Wingate is configured as the proxy server.

No, i'm not intercepting POP. The POP, DNS, IMAP and SMTP are all disabled in Wingate. Outlook is not using pop anyway. I should have mentioned that Outlook is connecting to the Exchange Server which is running on the same SBS box as Wingate.

Ian

[Hoof Hearted]

I've found out today that Outlook can be started with a /rpcdiag swithch in order to determine the connection type. I found that machines not running Wingate are connecting with http. Machines set to use the Wingate proxy server are connecting via TCPIP.

My guess is that they are failing to connect via http and using TCPIP instead, and somehow because of this the certificate error is being generated.

[adrien]

Hi

you talk about clients not running WinGate, and some are - is this the WinGate client software you're talking about?

Regards

Adrien