I can only imagine what happens to companies deploying an upgrade of either Exchange or Office. ![]() Test environment for a brand new Exchange 2010 deployment. While I can understand the principle of enforcing SSL security when making external connections, it's damned ridiculous to go through this rigamarole when simply setting up a The only way I was able to resolve it was by installing a trial cert from VeriSign, since even the AD issued by the domainĬA was not "trusted" by Outlook 2010 connecting via the internet. I have this problem as well with Outlook 2010 and not with OWA, iPhones, iPads or other mobile devices that can use ActiveSync. I'm at a loss as to what it could be tbh, i'm no exchange expert (this is my first attempt), just nobody else at work has any other idea so I was volunteered to try it out :) Made sure all exchange services are running RE-Created all the IIS Virtual directories (as per instructions here ) I know resolves on the machine, i've ensured RPC over HTTP is running on the exchange server, as well as enabled outlook anywhere. I've tried every possible combination of hostname which It's not firewall as i've even disabled firewall on the exchange server to test. I know it's not an issue with outlook (2010) as it has a connection to a different exchange 2010 server which works fine. Outlook must be online or connected to complete this action" The connection to microsoft exchange is unavailable. However, problems arise when I try to use outlook to connect, outlook simply won't do it, saying I've been tasked with trying out exchange server for our organisation, and I thought installation went well, all seemed to get setup correctly, OWA works perfetly and I can send and receive email to mailboxes on the domain.
0 Comments
Leave a Reply. |