Outlook will not connect to Exchange 2013

All replies

• 

  

  0

  Sign in to vote

  Hi

  As per the information and details provided by you, to connect outlook to exchange 2013, please follow these steps: -

  Use the following steps to setup your Microsoft Exchange 2013 mailbox with your Outlook email client.

  1. Click the Windows Start > Control Panel > Mail.

  Note: - Depending on the version of Windows you are running. You may need to switch to Classic view to find the Mail entry or it might be labeled 32-bit.

  1. Click Show Profiles > Add, enter a name of this profile, and then select OK.
  2. On the Auto Account Setup page of the Add New Account wizard, select Manually configure server settings or additional server types, and then click Next.
  3. On the Choose Service page, select Microsoft Exchange or compatible service, and then click Next.
  4. On the Server Settings page, perform the following actions:
     • In the Server text box, type Outlook.
     • Select the Use Cached Exchange Mode check box.
     • In the User Name text box, enter your email address.
     • Click More Settings.

  1. In the Microsoft Exchange dialog box, click the Connection > Connect to Microsoft Exchange using HTTP check box. Then, click Exchange Proxy Settngs.
  2. In the Microsoft Exchange Proxy Settings dialog box, perform the following actions:
     • In the Use this URL to connect to my proxy server for Exchange text box, enter mex06.emailsrvr.com.
     • Select both the On fast networks and On slow networks check boxes.
     • Under Proxy authentication settings, select Basic Authentication.
     • Click OK.
  3. In the Exchange dialog box, click Apply and then click OK.
  4. On the Server Settings page, click Check Name, type your password, and then Click OK.

  Note: If you receive a pop-up message asking you to select your mailbox from a list, select your mailbox and click OK.

  Your name will then be highlighted and a line will appear below the User Name field, which indicates your profile has been configured.

  Note: The server name resolves to a unique string that is different with every mailbox. Do not attempt to replicate this information with other accounts.

  1.  Click Next, and on the next page, click Finish.
  2. Open Outlook to select your new Exchange profile.

  Thanks and regards

  Shweta@G 

  
  

  • Marked as answer by Allen_WangJF Tuesday, April 7, 2015 1:32 AM
  • Edited by Goyal Shweta Monday, April 13, 2015 10:23 AM

  Tuesday, March 24, 2015 6:12 AM
• 

  

  0

  Sign in to vote

  Thank you - however, all mailboxes are still on EX2010 - just trying to get the environment pointed to 2013 so that it can proxy and we can start migrating mailboxes

  ---

  TAG

  Tuesday, March 24, 2015 2:28 PM
• 

  

  0

  Sign in to vote

  Please check this url and see if it is related to your issue.

  http://www.bctechnet.com/exchange-20102013-co-existence-experience/

  ---

  Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |

  Tuesday, March 24, 2015 7:21 PM
• 

  

  0

  Sign in to vote

  Well, the portion that does appear to be the same is that my 2010 ClientAccessArray points to Amail.domain.com (same as my internal Outlook Anywhere URL) - is there anyway around this, or do I have to change my 2010 CAS array (to point to each 2010 CAS)? 

  ---

  TAG

  Tuesday, March 24, 2015 9:54 PM
• 

  

  0

  Sign in to vote

  For testing purpose I would suggest to change Internal Outlook anywhere URL for exchange 2013 to something else then check if it is working.

  ---

  Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |

  Wednesday, March 25, 2015 4:25 AM
• 

  

  0

  Sign in to vote

  Hi,
   
  According to your description, I understand that Outlook client cannot connect to Exchange server when change DNS record to Exchange 2013 CAS.
  If I misunderstand your concern, please do not hesitate to let me know.
  
  I want to double confirm whether you change virtual directory and autodiscover DNS record to Exchange 2013.
  If not, please complete this migration first. I find an article about Step by step to migrate Exchange 2007 to Exchange 2013, for your reference:
  http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
   
  If issue persists, I recommend you run Microsoft Remote Connectivity Analyzer(https://testconnectivity.microsoft.com/) to get more details and also narrow down this issue. 
  
  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 tnmff@microsoft.com.

  Allen Wang
  TechNet Community Support

  

  • Edited by Allen_WangJF Wednesday, March 25, 2015 1:40 PM
  • Proposed as answer by Allen_WangJF Thursday, April 2, 2015 1:29 AM
  • Marked as answer by Allen_WangJF Tuesday, April 7, 2015 1:31 AM

  Wednesday, March 25, 2015 1:39 PM
• 

  

  0

  Sign in to vote

  Hello Therese,

  Presume you are using host files to override final DNS changes for your testing on the laptop/userPC?

  Sounds like Internal autodiscover works, and so does the OA connection to CAS 2013.
  Are you hit (ping, portqryUI to port 443) to Bmail.domain.com from that same laptop/userPC (put the external IP of Bmail.domain.com in the laptops host file)

  Some organizations do not allow an "intranet" connected machine to resolve or connect by going outside through DMZ and coming back in, to hit the external namespace. Since even lync breaks with Bmail.domain.com this smells more like a network config.

  Try the TestExchangeConnectivity, or even the offline client on the laptop PC
  https://testconnectivity.microsoft.com/

  • Proposed as answer by Allen_WangJF Thursday, April 2, 2015 1:28 AM
  • Marked as answer by Allen_WangJF Tuesday, April 7, 2015 1:31 AM

  Thursday, March 26, 2015 2:04 AM