Greetings to whoever has an answer to this riddle. Here's our environment: Our mail is hosted by another company. Sotheaddress"mail.ourcompany.com" is pointing to their IP address in the dns records. We have an exchange 2007 server which uses a 3rd party pop3 program to download the mail. Our mail is then processed by the exchange server, and distributed to our end users. Within my LAN I can browse to "https://mail.ourcompany.com" and gain access to the outlook web access. I have opened the appropriate port on my firewall and can now browse to my IP address externally, "https://xxx.xxx.xxx.xxx." The problem is, our certificates show "mail.ourcompany.com," so when I browse to web mail when outside my office I get a certificate error. Is there a way to set the certificate so that it uses the IP address forits friendly name to prevent Certificate errors? How should I proceed? Internally I have no certificate errors, only externally. cheers; Jordy

Hi, Have you considered to get another certificate like webmail.domain.com, install this on the Exchange server and then add the webmail hostname to the public dns?? Leif

Thats a great freakin' idea. I'm not sure why I didn't think of that. Thanks Leif! cheers; Jordy