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.

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

  • 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

  • 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

  • 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.

  • 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,

  • 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 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 2010 Will Not Connect to Exchange 2007 on SBS 2008 Server

    Good Morning,
    I have a user who cannot connect to the exchange server on SBS 2008 with outlook 2010.  When they start outlook, it shows disconnected and will not connect for a minimum of 20 minutes to an hour.  Any suggestions on how to fix this would be appreciated. 
    I have rebuilt their profile, but that does not fix the issue.
    Thank you,
    Lee F.
    Lee Feldman SMB Consultant

    Hi,
    Thanks for posting in the forum.
    Regarding the current issue, since you have recreated the user profile without any issue, I suspect that it’s mainly caused by the network issue. At this time, please first check the TCP/IP
    configurations as Larry mentioned. Then, please also refer to the article below for details about how to troubleshoot Outlook connectivity issue.
    Troubleshooting Microsoft Exchange: Outlook Connectivity Issues
    http://blogs.technet.com/b/mspfe/archive/2011/04/12/troubleshooting_2d00_microsoft_2d00_exchange_2d00_outlook_2d00_connectivity_2d00_issues.aspx
    Hope this helps.
    Best Regards,
    Andy Qi
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Andy Qi
    TechNet Community Support

  • Outlook 2010 clients connected to Exchange but not updating

    Hi, I am running a single Exchange 2013 server at CU6, with clients running Outlook 2010 with SP2.
    Clients are connected to Exchange without a problem, but Outlook is not updating, even though clients are set to do a full send/receive every 2 minutes. Users are getting new email on their phones but it doesnt arrive in Outlook even after a full 2 minutes. 
    By disabling Cached mode, Outlook then updates correctly. Checking the Connection Status, I find only 1 connection to Exchange. Ran the Auto-configuration test, and it's clean.  Ran tests at https://testconnectivity.microsoft.com/ and all was fine. I
    would appreciate any assistance.
    THANK YOU,
    Mike
    Regards, Mike

    Hello,
    From your description it sounds like there may be some corruption in the OST file (or maybe for some reason something else has the OST file locked).  Some things to try:
    Shutdown Outlook and make sure there are no Outlook.exe's running in task maanger.  Once that's done try to rename the user's OST file.  If you get an error saying the file is locked that's your issue.  You should be able to figure out what
    process has a lock on the OST file wiht either something like handles.exe or my personal favorite procmon.
    If you can rename the OST file without issue then that would point me to an issue with the OST file.  At that point I would try to create a new Outlook Profile in cached mode and recreate the OST file. 
    It also might be worth while installing the latest updates for Outlook 2010 if you haven't done so already (http://technet.microsoft.com/en-us/library/dn803988(v=office.14).aspx)

  • Outlook 2013 asks for credentials but does not connect for Exchange email, but only when out of office

    Hi,
    New employee wishes to use his Office 365. Have loaded onto new PC, connected to exchange, loaded his folders, everything is fine.
    When he leaves the office and connects at home, he is asked for credentials.
    I have tried the usual credentials: [email protected] and domain\user
    With each attempt, Outlook displays disconnected
    The password is correct, OWA he can log on fine, he has no problem when returning to the office. He has all the correct permissions in AD.
    No other user has a problem when away from the office, but every other user is using Office 2010
    Advice appreciated.

    Hi,
    Please make sure the user has enable Outlook Anywhere in Outlook.
    To turn on Outlook Anywhere, on the Connection tab, under
    Outlook Anywhere, check Connect to Microsoft Exchange using HTTP, and then click
    Exchange Proxy Settings. Your Exchange admin must enable this feature and provide you the proxy settings. For more information, please refer:
    http://office.microsoft.com/en-in/outlook-help/use-outlook-anywhere-to-connect-to-your-exchange-server-without-a-vpn-HP010355551.aspx
    Best Regards,
    Steve Fan
    TechNet Community Support

  • 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 can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

  • Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

    Greetings!  I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
    I am running into some odd behavior.  Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I  receive errors.  OWA works just fine for these Exchange
    2010 mailboxes, it is just Outlook that has the problem.  This is what I am running into:
    1. Outlook uses autodiscover to locate server settings.  It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
    2. It then gives me the settings box for Exchange server and Mailbox.  This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role).  If I then change the server to the Exchange 2010 CAS server,
    and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
    3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
    I've been doing as much research on this as I can.  I've tried disabling IPv6 to no avail.  It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards. 
    Any suggestions?  Thanks in advance!

    Hi,
    Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
    You can use your original SSL Cert for your new Ex 2013 environment.
    In dns you want two host A records: mail.domain.com and autodiscover.domain.com
    On your 2013 set your internal and external virtual directories to mail.domain.com
    leave autodiscover and Powershell alone.
    Also set the autodiscover URI to your Certificate name ie. mail.domain.com
    Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
    Thanks.  I wanted to give some additional info before I run any commands.  I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP.  I have a 3 entries for mail.domain, for DNS round robin; basically
    it is listed 3 times for the IP of each of my Exchange 2013 servers.  Does any of this sound problematic?

  • Outlook is not connecting through Workgroup Machine over internet using Outlook Anywhere

    users can connect successfully using outlook anywhere over internet if machine are on domain, well problem with workgroup machine that are not connecting over the internet as outlook keep prompting password well i have configured outlook Anywhere with
    default negotiate authentication as well as ssl offloading is checked and using same name for internal and external urls. also have valid 3rd party certificate configured on server.
    Talha Faraz Malik

    Hi,
    Step 1 :In addition to that , please use remote connectivity analyzer to check outlook anywhere in internet .
    From that we came to know the exact error .
    Step 2: Most of the organisations are having an ISA or TMG firewall to create web published rules for exchange services .In case if you have you need to check the rule created for outlook anywhere is properly configured or not.
    If you have such kind of firewall's ,You can test the OA rule by using the option test rule in ISA or TMG firewall .
    Most probably you can able to find out the exact cause with the help of EXRCA.
    Please reply me if you have any queries.
    Regards
    S.Nithyanandham

Maybe you are looking for