I have a setup at my desk where I connect my computer to a an RJ45 switch that switches between two networks. One network is the corporate network, which is maintained by my company's IT, and the other is my own private network where I do testing (the two networks have to be separated). The corporate network hosts the exchange server where I get e-mail. When I switch from the private network to the corporate network, I expect Outlook to re-connect to the exchange server. However, I have found that sometimes when I come back, Outlook take an extremely long time to re-connect. Send/Receive will give me back the error 'The server is not available' (0x8004011D). It will sit there for 10 minutes to a few hours before it finally re-connects.
Jun 21, 2016 - We support the latest versions of Apple Mail and Calendar for Mac OS. With the IT professional in your department if you are having problems. First I would like to confirm if you use Exchange account in Outlook 2016 for Mac, if yes, I suggest you try the methods in this article to see if the issue can be solved If not, I suggest you do the following troubleshooting steps.
The only other option is to reboot my computer, which is a huge pain for me since I run multiple VMs on it. This usually happens when I'm connected to the private network for a significant amount of time, so I'm thinking it's because Outlook has cached the network status. Is there a way to force Outlook to do a 'hard' re-connect to the exchange server?
I'm using Windows XP SP 3 with Outlook 2007.
200 Windows users, only 1 Mac user. All Outlook 2010/2013 is working fine. OUtside the office Outlook for Mac cannot connect to the exchange server. In the office, Outlook for Mac is working. On the Mac there is a mail program also working with Exchange from office or outside.
From testing, seems Outlook for Mac cannot get a right external server address, donnot know why. Server: exchange 2010 sp3. Client:Office for Mac 2011 Action early taken: Uninstall the latest rollup patch on exchange server and Mac, no result.
Any comment is appreciated. Outlook clients on domain-joined machines internally connecting don't use the same Autodiscover URL, theirs is supplied by Set-ClientAccessServer -AutodiscoverServiceInternalUri, so that could be why you don't see the problem with them. Tell us exactly and completely what you're doing and what you're seeing, like a lot more context about what exactly is failing in ExRCA, and maybe we can be of more assistance. Ed Crowley MVP 'There are seldom good technological solutions to behavioral problems.' Celebrating 20 years of providing Exchange peer support! Hi David, Welcome to our forum.
Please make sure Exchange server wasn’t configured with Strict mode, because outlook for Mac uses SSL to establish communication with an Exchange server, we could refer to the following link: If the issue persist, we suggest you post this case by the following link: Best Regard, Jim Xu Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]. Jim Xu TechNet Community Support. Outlook clients on domain-joined machines internally connecting don't use the same Autodiscover URL, theirs is supplied by Set-ClientAccessServer -AutodiscoverServiceInternalUri, so that could be why you don't see the problem with them. Tell us exactly and completely what you're doing and what you're seeing, like a lot more context about what exactly is failing in ExRCA, and maybe we can be of more assistance. Ed Crowley MVP 'There are seldom good technological solutions to behavioral problems.' Celebrating 20 years of providing Exchange peer support!
The reslut of autodiscovery test as below: AutoDiscoverConnectivityFailed We were not able to successfully connect to Autodiscover SmtpDomain xxx.com AutoDiscoverTargetEmailAddress AutoDiscoverResultingEmail AutoDiscoverExternalMailboxServer AutoDiscoverInternalRpcClientServer AutoDiscoverAuthenticationType Basic AutoDiscoverUserDn AutoDiscoverHomeMdbDn AutoDiscoverUserDomain OutlookAnywhereConnectivitySucceeded We were able to successfully connect to your email server via the Outlook Anywhere feature. The Microsoft Connectivity Analyzer is attempting to test Autodiscover for test@ xxx.com Testing Autodiscover failed. Additional Details Test Results Attempting to resolve the host name xxx.com in DNS.
The host name couldn't be resolved. Tell me more about this issue and how to resolve it Additional Details Testing Outlook connectivity.
The Outlook connectivity test failed. Additional Details Elapsed Milliseconds: 381279 Test Results. Detailed test as below.
Exchange Web Services synchronization, notification, availability, and Automatic Replies. Tests of all Exchange Web Services tasks completed successfully. Additional Details Elapsed Time: 92015 ms. Test Steps The Microsoft Connectivity Analyzer is attempting to test Autodiscover for test @ xxx.com Autodiscover was tested successfully. Additional Details Elapsed Time: 6821 ms.
Test Steps Attempting each method of contacting the Autodiscover service. The Autodiscover service was tested successfully.
Additional Details Elapsed Time: 6821 ms. Test Steps Attempting to test potential Autodiscover URL https: //autodiscover.xxx.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed. Additional Details Elapsed Time: 17 ms. Test Steps Attempting to resolve the host name xxx.com in DNS. The host name couldn't be resolved.
Additional Details Host xxx.com couldn't be resolved in DNS InfoNoRecords. Elapsed Time: 17 ms. Attempting to test potential Autodiscover URL https: //autodiscover.xxx.com:443/Autodiscover/Autodiscover.xml Testing of the Autodiscover URL was successful. Additional Details Elapsed Time: 6803 ms.
Test Steps Attempting to resolve the host name autodiscover.xxx.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: x.x.x.x Elapsed Time: 14 ms.
Testing TCP port 443 on host autodiscover.xxx.com to ensure it's listening and open. The port was opened successfully. Additional Details Elapsed Time: 307 ms. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements.
Additional Details Elapsed Time: 670 ms. Test Steps The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xxx.com on port 443. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=.xxx.com, OU=Domain Control Validated - RapidSSL(R), OU=See.com /resources/cps (c)12, OU=GT00472335, SERIALNUMBER=vdoPYuyuXZuxIu6LJ4bPI3GyEhIIu5rB, Issuer: CN=RapidSSL CA, O='GeoTrust, Inc.'
Elapsed Time: 628 ms. Validating the certificate name. The certificate name was validated successfully.
Additional Details The host name that was found, autodiscover.xxx.com, is a wildcard certificate match for common name.xxx.com. Elapsed Time: 0 ms. Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain. Test Steps The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=.xxx.com, OU=Domain Control Validated - RapidSSL(R), OU=See /resources/cps (c)12, OU=GT00472335, SERIALNUMBER=vdoPYuyuXZuxIu6LJ4bPI3GyEhIIu5rB.
One or more certificate chains were constructed successfully. Additional Details A total of 1 chains were built. The highest quality chain ends in root certificate CN=GeoTrust Global CA, O=GeoTrust Inc., C=US.
Elapsed Time: 13 ms. Analyzing the certificate chains for compatibility problems with versions of Windows. Potential compatibility problems were identified with some versions of Windows. Additional Details The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the 'Update Root Certificates' feature isn't enabled. Elapsed Time: 2 ms.
Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 6/19/2012 2:25:59 AM, NotAfter = 6/21/2016 6:17:49 AM Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Elapsed Time: 1428 ms. Attempting to send an Autodiscover POST request to potential Autodiscover URLs. The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST. Additional Details Elapsed Time: 4383 ms.
Test Steps The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https: // autodiscover.xxx.com: 443/Autodiscover/Autodiscover.xml for user test @ xxx.com The Autodiscover XML response was successfully retrieved. Additional Details Autodiscover Account Settings XML response: Elapsed Time: 5757 ms.
Setting and retrieving user OOF settings. The user's Automatic Replies (OOF) settings were set and retrieved successfully.
Additional Details Elapsed Time: 15304 ms. Test Steps Getting user Automatic Replies (OOF) settings and confirming them against expected values. The Microsoft Connectivity Analyzer successfully retrieved and confirmed user OOF settings. Additional Details Elapsed Time: 2066 ms.
Setting the user Automatic Replies (OOF) settings. The user's Automatic Replies (OOF) settings were set successfully. Additional Details The user's new OOF settings were set successfully.
Last EWS request: Elapsed Time: 8006 ms. Getting user Automatic Replies (OOF) settings and confirming them against expected values. The Microsoft Connectivity Analyzer successfully retrieved and confirmed user OOF settings.
Additional Details The new Automatic Replies (OOF) settings were verified. Last EWS request: Elapsed Time: 3136 ms. Setting the user Automatic Replies (OOF) settings.
The user's Automatic Replies (OOF) settings were set successfully. Elapsed Time: 2094 ms.