Installed certificate now Exchange 2013 is unavailable!?
Just configured my Exchange server an started connecting clients
when Outlook was opening on the clients, a security dialoge was opening about Certificate giving me an option of installing said certificate.
once the certificate was installed, the dialogue disappeared an i was able to carry on.
However, since then i have been unable to connect to the Exchange from that server.
I can access Exchange from all the other machines in the domain.
is it just a case of uninstalling that certificate?
thanks
(really confused)
when Outlook was opening on the clients, a security dialoge was opening about Certificate giving me an option of installing said certificate.
once the certificate was installed, the dialogue disappeared an i was able to carry on.
However, since then i have been unable to connect to the Exchange from that server.
I can access Exchange from all the other machines in the domain.
is it just a case of uninstalling that certificate?
thanks
(really confused)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please can you post all common names of the certificate.
Also post your Outlook Anywhere configuration. Remember exchange 2013 uses Outlook anywhere even to connect internally on your network so your cert names has to correspond to Outlook anywhere configs and DNS entries.
Also post your Outlook Anywhere configuration. Remember exchange 2013 uses Outlook anywhere even to connect internally on your network so your cert names has to correspond to Outlook anywhere configs and DNS entries.
ASKER
Hi common name is mail.domainname.com
From Servers > virtual directories > OWA
internal URL - https://mail.domainname.com
External URL - https://mail.domainname.com
im confused :(
From Servers > virtual directories > OWA
internal URL - https://mail.domainname.com
External URL - https://mail.domainname.com
im confused :(
ASKER
This might be something...or nothing?
autodiscovery configs....
our internal domain is HFT.ds
our web domain name is HFTLTD.com
it seems exchange is trying to use our internal domain instead of our web domain - if that makes sense?
autodiscovery configs....
our internal domain is HFT.ds
our web domain name is HFTLTD.com
it seems exchange is trying to use our internal domain instead of our web domain - if that makes sense?
It makes sense hence you need to look at DNS records.
You should have external dns records on your local dns records pointing mail and autodiscover records to your CAS server on domainname.com.
You should have external dns records on your local dns records pointing mail and autodiscover records to your CAS server on domainname.com.
ASKER
ok, i may have made things worse...
following this http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
i changed our autodiscovery to try an match our domain using
now my outlook profile can not connect
following this http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
i changed our autodiscovery to try an match our domain using
Set-ClientAccessServer -Identity MAILSERVER -AutoDiscoverServiceInternalUri https://autodiscover.domainname.com/Autodiscover/Autodiscover.xmlnow my outlook profile can not connect
No that is correct.
Like i said go to your internal DNS server. Do you have a zone for your external domain?
Like i said go to your internal DNS server. Do you have a zone for your external domain?
ASKER
It was the certificate!!
renewed the certificate with another supplier an now we are back in business
thanks
renewed the certificate with another supplier an now we are back in business
thanks
ASKER
im getting other issues now - i deleted the certificate in question on the effected server, an im now able to access Exchange
certificate is for mail.domainname.com but the message that comes up with Outlook etc is the fqdn of the server!?