Outlook 2011 not connecting to exchange server

Hi,
I am trying to use outlook 2011 with my Mac to connect to my Company server Exchange with no success
while I can do it fine with the Mac native aplication "Mail".
Here after the Exchange Server Connectivity Test (in italian) which has been passed:
Altri dettagli Impostazioni account del servizio di individuazione automatica Risposta XML: <?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User> <DisplayName>GGGGG GIAMBERTO</DisplayName> <LegacyDN>/o=Messaging/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=U333</LegacyDN> <DeploymentId>4e25f968-2a52-4b3e-a495-85893d549218</DeploymentId>
</User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>outlook-to.sede.corp.NN.com</Server> <ServerDN>/o=Messaging/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=outlook-to.sede.corp.NN.com</ServerDN> <ServerVersion>7383807B</ServerVersion> <MdbDN>/o=Messaging/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=outlook-to.sede.corp.NN.com/cn=Microsoft
Private MDB</MdbDN> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> <OOFUrl>https://webmail-01.XX.com/ews/exchange.asmx</OOFUrl> <OABUrl>https://webmail-01.XX.com/OAB/8b29a335-91f9-459d-8226-af3af35a0f11/</OABUrl>
<UMUrl>https://webmail-01.XX.com/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <PublicFolderServer>EXC10TSPPF00.sede.corp.NN.com</PublicFolderServer>
<AD>RSDCFTS008.filiali.corp.NN.com</AD> <EwsUrl>https://webmail-01.XX.com/ews/exchange.asmx</EwsUrl> <EcpUrl>https://webmail-01.XX.com/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
</Protocol> <Protocol> <Type>EXPR</Type> <Server>webmail.XX.com</Server> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> <OOFUrl>https://webmail-01.XX.com/ews/exchange.asmx</OOFUrl> <OABUrl>https://webmail-01.XX.com/OAB/8b29a335-91f9-459d-8226-af3af35a0f11/</OABUrl>
<UMUrl>https://webmail-01.XX.com/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage>
<CertPrincipalName>msstd:webmail.XX.com</CertPrincipalName> <EwsUrl>https://webmail-01.XX.com/ews/exchange.asmx</EwsUrl> <EcpUrl>https://webmail-01.XX.com/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
</Protocol> <Protocol> <Type>WEB</Type> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <Internal> <OWAUrl AuthenticationMethod="Basic, Ntlm, Fba, WindowsIntegrated">https://webmail-01.XX.com/owa/</OWAUrl>
<OWAUrl AuthenticationMethod="Ntlm, WindowsIntegrated">https://webmailint-01.XX.com/owa/</OWAUrl> <OWAUrl AuthenticationMethod="Basic, Ntlm, WindowsIntegrated">https://webmailint-01.XX.com/owa/</OWAUrl> <Protocol>
<Type>EXCH</Type> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> </Protocol> </Internal> <External> <OWAUrl AuthenticationMethod="Fba">https://webmail-01.XX.com/owa/</OWAUrl> <Protocol>
<Type>EXPR</Type> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> </Protocol> </External> </Protocol> </Account> </Response> </Autodiscover> Intestazioni risposte HTTP: Connection: Keep-Alive
Transfer-Encoding: chunked Persistent-Auth: true Cache-Control: private Content-Type: text/xml; charset=utf-8 Date: Wed, 11 Feb 2015 05:31:48 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Tempo trascorso: 1894 ms.
And hereafter the Trouble shooting log of Outlook 2011:
Outlook Exchange Auto Configure,Verbose,=== Performing autodiscover for [email protected]
Outlook Exchange Auto Configure,Verbose,--- HTTPS endpoints
Outlook Exchange Auto Configure,Verbose,Querying https://xx.com/autodiscover/autodiscover.xml
Outlook Exchange Web Services,Verbose,"EWS: Request data on thread=0x7a2bf264, XML data=
<?xml version=""1.0"" encoding=""UTF-8""?><soap:Envelope xmlns:soap=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:t=""http://schemas.microsoft.com/exchange/services/2006/types""
xmlns:m=""http://schemas.microsoft.com/exchange/services/2006/messages""><soap:Header><t:RequestServerVersion Version=""Exchange2007_SP1"" /><t:MailboxCulture>it-IT</t:MailboxCulture><t:TimeZoneContext><t:TimeZoneDefinition
Id=""XXX Standard Time""/></t:TimeZoneContext></soap:Header><soap:Body><GetFolder xmlns=""http://schemas.microsoft.com/exchange/services/2006/messages""><FolderShape><t:BaseShape>IdOnly</t:BaseShape></FolderShape><FolderIds><t:DistinguishedFolderId
Id=""inbox""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""outbox""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""contacts""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""calendar""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""notes""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""tasks""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""journal""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""sentitems""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""deleteditems""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""drafts""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""junkemail""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""root""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId></FolderIds></GetFolder>"
2015-02-28 11:44:10.075,0xFFFFFFFF,Outlook Exchange Web Services,Info,"EWS: Sending request on connection=0x7a399eb8, URL=/ews/Exchange.asmx, SoapAction=""http://schemas.microsoft.com/exchange/services/2006/messages/GetFolder"""
Outlook Exchange Auto Configure,Error, Error code: -3259
Outlook Exchange Auto Configure,Verbose,Querying https://autodiscover.xx.com/autodiscover/autodiscover.xml
Outlook Exchange Auto Configure,Error, Error code: -39
Outlook Exchange Auto Configure,Verbose,--- HTTP redirect endpoint
Outlook Exchange Auto Configure,Info, Error code: -3259
Outlook Exchange Auto Configure,Verbose,--- DNS SRV method
Outlook Exchange Auto Configure,Error, Error code: -3176
Outlook Exchange Auto Configure,Verbose,No _autodiscover._tcp.xx.com service found
Outlook Exchange Auto Configure,Verbose,--- HTTPS endpoints
Outlook Exchange Auto Configure,Verbose,Querying https://webmail.xx.com/autodiscover/autodiscover.xml
Outlook Exchange Auto Configure,Error, Error code: -39
Outlook Exchange Auto Configure,Verbose,Querying https://autodiscover.webmail.xx.com/autodiscover/autodiscover.xml
Outlook Exchange Auto Configure,Error, Error code: -3259
Outlook Exchange Auto Configure,Verbose,=== Failed to retrieve autodiscover settings for [email protected]
Outlook Exchange Web Services,Verbose,"EWS: Request data on thread=0x7c20cee4, XML data=
Can somebody help?
Thank you in advance

Hi,
The connection in Outlook 2011 for Mac is difference from the Exchange connection in Outlook for Windows. The Outlook for Mac is using EWS for Exchange connection.
According to your original posting, there seems to be some issue with your autodiscover service. And some Exchange services (such as OAB, OOF, OWA etc.) are using webmail-01.xx.com namespace in the URL. Please double confirm the configuration in your Exchange
server.
Additionally, please check the autodiscover service on Outlook for Windows machine. If all configurations in server side are correct but the issue persists, I suggest we can ask a question in Outlook 2011 for Mac forum for more help:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

XP Outlook 2007 not connecting to exchange server for office365 mail

Here is the deal it is the workstation it self no one can get there account to connect through outlook on the work station the person who's work station it is can connect with outlook on other work stations.
1. First thing it does is continues to prompt for user name/ password window.
2. After 2 popups of name/ password It states "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must
be online or connected to complete this action."
3. I have then gone through control panel > mail > Show Profiles > Removed the only profile > Add profile > Pop-up for username/ password appears > fill it in > Add new email account then pops-up > fill in Name, Email Adress,
Password, Retype Password > Configuring - green checkmark on "Establish network connection" - bullet arrow at "Search for johndoe@blankcom server settings" then pop-up for "User Name: Password:" form filled in
- pop-up reappears and form filled out for 10 times > cancel > pop-up "The action cannot be complerted. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." >
Click "OK" > Microsoft Exchange form pop-up "Microsoft Exchange server:/Mailbox:" form is already filled out Click "OK" > pop-up "The action cannot be complerted. The connection to Microsoft Exchange
is unavailable. Outlook must be online or connected to complete this action." but green Check mark next to "Search for johndoe@blankcom server settings" > pop-up "The action cannot be complerted. The connection
to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." Click "OK" > Verify Settings form appears "E-mail Adress: Password: Retype Password:" form filled out click "Retry"
> green check mark turns to bullet arrow at "Search for johndoe@blankcom server settings" the back to pop-up "The action cannot be complerted. The connection to Microsoft Exchange is unavailable. Outlook must be online
or connected to complete this action." > Click "OK" > Microsoft Exchange form pop-up "Microsoft Exchange server:/Mailbox:" form is already filled out Click "OK" > Cannot Log on to Server
> I cancel and seek help
3. Have ran MCATest Results are auto discover successful with errors. Errors are as follows
1>Testing TCP port 443 on host dot.ny.gov to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Additional Details
A network error occurred while communicating with the remote host.
2> 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.
Please help

Yes we have narrowed it back to the workstation as the user can sign on other workstations through outlook and when using the control right click and checking connectivity activity. This work station tries to connect to the right server name as the
one that does connect. But it hangs up there using the same server name, type- directory, status-connecting then asks for user name password. No change is status after it is filled out and OK is pressed.

Issues connecting Outlook 2011 for Mac to Exchange Server 2013

Could someone help me with the bellow please:
I have a Mac with outlook 2011 on it.
We have recently set up Exchange Server 2013, and all of the Windows Workstation just required the trusted root certificate to be installed and they were working.
However I have spent hours reading different forums trying to get this working on the Mac and no luck.
The auto discover does not work when setting up the exchange email, therefore I have also tried setting up manually but it still will not connect to the server.

Hi,
Please check if the links below help:
How the Autodiscover service works with Outlook for Mac 2011:
http://technet.microsoft.com/en-us/library/jj984202(v=office.14).aspx
A great tool for troubleshooting Autodiscover and Outlook 2011 for Mac connectivity issue:
http://blogs.technet.com/b/johnmak/archive/2012/04/01/a-great-tool-for-troubleshooting-autodiscover-and-outlook-2011-for-mac-connectivity-issue.aspx
Since this forum is for general questions and feedback related to Outlook for Windows, it's better to post your question to the forum for Exchange or for Mac:
Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
Office for Mac forum:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly
can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support

Outlook Mac Loses Connection to Exchange Server

Hi All,
I've had this problem pretty since deployment a couple of weeks ago, so I'm hoping some one can point me in the right direction. I'm running Exchange 2013 on a Server 2012 Standard box with the DC running on a different box, every thing up to date.
Mac clients running Outlook 2011 (14.4.2).
Periodically throughout the day, Outlook loses connection to Exchange server. After several minutes, it will connect back up, and seems to operate normally. During the down time, I am able to connect to OWA, and ActiveSync seems to work as well.
If I run the Remote Connectivity Analyzer while Outlook is responding, I get no errors and the "Connectivity Test Successful" message. However, if I run it while Outlook is NOT responding, I get the following:
Exchange Web Services synchronization, notification, availability, and Automatic Replies.
Not all tests of Exchange Web Services tasks completed.
Creating a temporary folder to perform synchronization tests.
Failed to create temporary folder for performing tests.
Exception details:
Message: The request failed. The operation has timed out
Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
Stack trace:
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
Elapsed Time: 100141 ms.
Nothing I've attempted to do so far as had any meaningful impact, and I am fairly new to Exchange.
Following the adice I've seen online so far, I've:
I've made sure the auto discover in DNS points to the Exchange server.
I've disable auto-discover on the client, manually adding accounts, tried using their FQDN, local IP, LAN IP.
I've made exceptions to the proxie on the client.
Just not sure where to look next? Appreciate any advice out there.
Thanks,
Michael

Hi,
Before we go further, I'd like to confirm if your Outlook clients can work well when your Outlook MAC clients come across the issue.
If the issue only happens on your Outlook MAC clients, we can check the IIS log and confirm if there is any error releted to EWS. And you can recreate your EWS virtual directory to have a test.
Thanks,
Angela Shi
TechNet Community Support

Outlook Can't connect to Exchange Server

Dear All;
I install the exchange server 2013 in our Environment with basic configurations, it was work correctly in out look and OWA.
In this period I install outlook Clint and connect to exchange correctly , Then I log in to Exchange Administrations Center , then make some changes , after that i can't connect outlook Clint to exchange server while I
can connect to OWA but with error message related to Certificate.(Kindly check the screen shoot of error )
Kindly help me to solve this issue I beginner with Exchange.

Here are the default permissions for the Exchange virtual directories:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
I found that the print in the screenshots was not clear - maybe it's me or my browser.
What names do you have on the certificate?
exchange.abc.local
Is that it?
Is this a self-signed certificate? Or did you get it from Digicert, VeriSign, GoDaddy or some other 3rd party authority?
Regardless, the URLs for the virtual directories, OWA in particular, have to match what is on the cert.
So OWA might be:
https://mail.exchange.abc.local/owa
Other possibility:
https://webmail.exchange.abc.local/owa
Since exchange.abc.local is what you have on the cert, the URL has to configured as shown above. You can use "mail", "webmail" or whatever just before (once again, as shown above) but you have to make sure that is what the users enter
when they attempt to access email.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook 2011/365 connectivity to Exchange 2010

Hey Everybody,
I'm running into a little bit of jam with Outlook 2011/365 from my Mac population to Exchange 2010 SP3 Rollup 8 v2. I have read many articles and discussion forums regarding the issues with SSL and TLS connectivity. I have verified that my windows host with
Outlook are just fine in setup and use of the Exchange server.
The Mac systems are having the issues. Autodiscover is working ok and IPhone/Ipad configure just fine. We really only have two, so this is why it was a surprise.
If I browse to the EWS directory it is just a blank page receive from any browser on the Mac's.
What is the issue with Outlook 2011 and 365 connecting to a exchange system during configuration?
Would joining the Mac's to the domain make a difference?
With Poodle being one of the most recent risks, what should Mac user be configured as to not bring a security risk to the rest of the environment.
Is reseting the virtual directories a possible action or is the most common issue just SSL and TLS compatibility?
Is there anyways around this without having to turn on basic security on EWS and fall back to SSL instead of TLS?
What is the best ways of testing connectivity with logging other then just seeing the error 17997 from Outlook on the Mac.
Thoughts? Recommendations? Tips?
Thanks,
Matthew

Hi Matthew,
According to your description, I noticed that the issue doesn’t happen in Outlook for Windows but occurs in Outlook 2011 for Mac.
Please access the EWS URL from Internet Explore in Windows instead of Mac machine, and check whether a proper XML file is returned. If the XML file returns in Windows for the problematic account, it indicates the EWS service should be working in Server side.
The issue may be related to client side in Outlook 2011 for Mac machine, I suggest we can ask a question in Outlook for Mac forum for more help:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
If the EWS service doesn’t work in Windows either, please check whether users can view free/busy information in OWA. Then run the following command to check the EWS configuration in server:
Get-WebServicesVirtualDirectory | FL Identity,*AUTH*,*url*
Regards,
Winnie Liang
TechNet Community Support

Outlook does not connect to Exchange 2013 after name change due to marriage

When launching Outlook and clicking through the setup wizard to create a new profile, Outlook auto-discovers the correct email alias. When establishing a connection it successfully checks network connectivity and successfully searches the email settings.
When it attempts to logon to the mail server the error comes up.
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
Clicking "Check Name" gives the error:
"The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
The same result occurs with a manual setup.
We are running Exchange Server 2013. User workstations are running Outlook 2013 on Windows 7 Pro. All updates have been applied as of March 31, 2015.
All name changes have been made in AD and Exchange. Old aliases and new aliases are set in Exchange. Offline Address books are updated daily. The local profile and registry settings have been updated on the workstation and the user is successfully logging
into the profile. The issue is only with Outlook 2013. User can access mail through OWA and ActiveSync on their mobile device.
Logging the user into another workstation and running the wizard returns the same results, which rules out the possible problem being with the workstation.

Hi,
According to your description, I understand that failed auto-configure Outlook with error “The name cannot be resolved. The connection to Microsoft Exchange is unavailable…”, however OWA works fine.
If I misunderstand your concern, please do not hesitate to let me know.
Are all account or any special user experience this question?
If OWA works fine, it indicate that the mailbox database is mounted, and mailbox works well.
I notice that you have changed the account name before issue arise, because external access, the client locates the Autodiscover service on the Internet by using the primary SMTP domain address from the user's email address.
More details about Autodiscover service, for your reference:
https://technet.microsoft.com/en-us/library/bb124251.aspx?f=255&MSPPError=-2147217396
Please try below command to force update address list, GAL, OAB, then test again:
Get-AddressList | update-AddressList
Get-GlobalAddressList | update-GlobalAdressList
Get-OfflineAddressBook | Update-OfflineAddressBook
If the issue persists, please wait for some time to complete configuration.
Thanks
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]
Allen Wang
TechNet Community Support

Microsoft Outlook 2010 cannot connect to exchange server

I have just got Microsoft Outlook 2010 and I cannot open it.
When I click to open it I get an error message saying that "the connection to microsoft exchange is unavailable. Microsoft must be online or connected to complete this action"
I have checked my connection www.testexchangeconnectivity.com
and everything is OK here. I can connect through owa and I use the exchange server on my ipad and my phone so I have no idea what is going on.
I have tried lots of other solutions that have been on forums but none of them have worked for me. Please can you help?
Kind Regards
Damian
PS apologies for the green text but I copied and pasted the web link and could not get rid of the green text afterwards!

Hi,
If you test on www.testexchangeconnectivity.com is ok.
Maybe it has some issue on Client setting.
So please check if client setting is correct and if you fill the DNS server on client and can resolve the Exchange URL.
Wendy Liu
TechNet Community Support

Outlook RT not connecting to Exchange

Outlook RT will not connect to our Exchange Server. The W8 Mail app connects with no problem and have been using since the start. It cannot resolve the username and will not connect even though it asks for and accepts
my Exchange password. I contacted Surface tech support and they were absolutely clueless. No help at all. Is there anything special that needs to be done on the MS Exchange side for Outlook for RT. We connect with iDevices and W8 Phones
using Activesync with no issues. I realize this is a "Preview" release but you would think the tech support would at least propose some reasonable fix suggestions. The support person seemed to be looking on blogs for help while I sat
on the phone...dissapointing.

I get all that, and my RTs are configured. I've even got scripts to automate the process when a new user account is added to the device.
I think Mattias had the clearest response on the issue and since then we've all moved on.
What I'm saying is that why do we have to manually configure outlook on an RT for an on-prem connection even though every other device that we can throw at it (being the exchange server) just auto connects.
What I don't have are SRV records in the public DNS, and that probably might be a cause, but like others commenting in this thread I don't get the logic behind an MS device that is so far the only device that I can't get to automatically connect to my MS
environment.
What really weirds me out is that I can even get the standard RT mail client to connect to my exchange via autodiscover, but not outlook.
So I'd like to skip as much of the usual diagnostic info as I can and reiterate that for my domain the Remote Connectivity Analyzer reports everything as configured correctly, if it didn't I'd be back on same noob forum and certainly not in here.

Outlook icloud not connecting to mail server

I had to reset my icloud password. When I opened up Outlook on my PC, all my icloud mail folders were gone. I have set up icloud control panel and my email address over and over. Outlook (icloud) will not connect with the mail server. My other emails do not have this problem.

Post the settings you are using (it's not snmp, it's smtp)
Or
Follow these:
IMAP (Incoming Mail Server) information:
Server name: imap.mail.me.com
SSL Required: Yes
Port: 993
Username: [email protected] (use your @me.com address from your iCloud account)
Password: Your iCloud password
SMTP (outgoing mail server) information:
Server name: smtp.mail.me.com
SSL Required: Yes
Port: 587
SMTP Authentication Required: Yes
Username: [email protected] (use your @me.com address from your iCloud account)
Password: Your iCloud password
Note: If you receive errors using SSL, try using TLS instead.

OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanks

Hi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang

Outlook 2007 does not connect to exchange at computer startup

Hi all :)
Here's the situation we're encountring: we are using exchange 2010 with outlook 2007 clients. The issue is that at the startup of the computer, outlook does not connect to exchange (it opens up but it marks that it's not connected to exchange). After trying
a few times it connects and stays stable (if I close outlook and I open it again, it connects normally).
This suggests that there's may be a DNS problem: The client is having an issue resolving the name, but once it does and the IP of exchange is available in the cache, outlook doesn't face any issues.
So I ran some nslookup commands and I noticed the following:
when I try to resolve the name of exchange, the request times out twice before providing the answer.
This issue occurs only for forward lookups (when I try to resolve the same IP for the hostname, there's no timeout)
I also noticed that this issue only occurs when I run nslookup from the client machines (no timeout when I run it from exchange for instance).
Any ideas about what the problem might be? Could it be something else other than DNS?
Thank you all for your help.

Hi all,
The problem seems not to be related to DNS. Our exchange 2010 organization was actually migrated from a 2007 one. Since then we noticed this issue of outlook taking too much time to connect and sometimes disconnects. I was messing around into adsiedit and
I noticed that a decomissioned Mailbox Server from our old exchange 2007 organization still exists among the new exchange 2010 objects.
To further look into it, I ran best practise analyser, the result (to my surprise) was that exchange is still trying to contact the old exchange 2007 server.
I ran some network trafic captures with Network Monitor, but I was not very successful interpreting anything.
I uploaded the .cap files with the best practise analyser report and a print screen of the old server into adsiedit objects. I hope you'll be able to help with it.
I took the network captures on the two CAS Servers (configured in a CAS array) and on a client machine. The IP addresses are as follow:
client 192.168.0.47
Domain Controller1 192.168.1.205
Domain Controller2 192.168.1.213
CAS1 192.168.2.216
CAS2 192.168.2.217
CAS Array 192.168.2.218
Download Link: https://onedrive.live.com/redir?resid=9360346C01880F58%21935
Thanks,

Cant Get Mac Mail ( or Outlook 2011) to connect to Excange erver

When connecting via IPAD it took 30 seconds to set up.
I cant get it running from MAC Mail nor Outlook 2011 for MAC.
Exchange "Server not responding".
It runs great from Outlook Web Access on the mail or from VmWare running Win 7 with Outllok 2007
H E L P !!

+1. Me, too. Any solutions? Every few months I spend a lot of time looking for workarounds for this issue. I tried with Mail, and recently I tried the new Microsoft Office. No luck. I work from home and the company I work for uses an exchange server. I'm stuck with Entourage 2008. It's a real bummer.

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2011 not connecting to exchange server

Similar Messages

Maybe you are looking for