Improve company productivity with a Business Account.Sign Up

x
?
Solved

On-site users cannot authenticate to Exchange server after power-shell changes; OWA works fine?

Posted on 2014-02-26
2
Medium Priority
?
1,220 Views
Last Modified: 2014-05-07
We have been having a ton of certificate errors, due to our internal domain being "domain.local", and only having a single Exchange server with a wildcard cert "*.domain.local". To ensure that all Outlook users would connect directly to the external address (which had the proper certificate), I changed all of the internal/external settings in these instructions (http://exchangeserverpro.com/avoiding-exchange-2013-server-names-ssl-certificates/) to https://external.domain.com/_____.

Tested it on a few machines, no problems. The next day (today), getting 50% of users internally reporting that they cannot connect - keeps popping up user/pass window... Try to authenticate (domain\user and applicable password), but only get this error: "The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action." So far, no issue configuring externally, and the "Remote Connectivity Analyzer" shows no issues in any category.

OWA works fine, and as I mentioned, about 50% of users work normally after reboot. Stumped - can anyone help?
0
Comment
Question by:ITAdvisors
2 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39889317
Does the external name resolve internally?
If you run an Autodiscover test, do the correct host names come back?

Simon.
0
 
LVL 44

Accepted Solution

by:
Adam Brown earned 2000 total points
ID: 39889556
More than likely the autodiscover settings are cached with the old name of autodiscover.domain.local, so computers are getting screwed up. Try running a repair on the Outlook profile for a user who has the issue to see if that fixes the problem. If it doesn't, remove any autodiscover.domain.local entries in DNS, Then create a SRV record in the domain.local DNS zone for the _autodiscover service that points clients to the autodiscover.domain.com address. http://acbrownit.wordpress.com/2012/12/20/internal-dns-and-exchange-autodiscover/ has info near the bottom on configuring a SRV record.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Are you working to mount the dismounted Exchange 2013 database? Then the best course of action is to analyze the causes of Database issue, their probable solutions and decide for the appropriate course of action.
Microsoft Exchange Server gives you the ability to roll back a corrupt database, but still preserve any data written to that database since the last successful backup. Unfortunately the documentation on how to do this when recovering using imaging b…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, just open a new email message. In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

606 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question