connect outlook to exchange server 2013 over internet

#Connect outlook to exchange server 2013 over internet update
#Connect outlook to exchange server 2013 over internet manual
#Connect outlook to exchange server 2013 over internet series

My question are why mobile devices works without any problem? and how can I make Outlook works without modifying anything on server side. Some are running Outlook 97, others have Outlook 2000. At the customer site, there are 50 laptops running 95 or 98. Maybe if we can get everyone with the problem on the same thread, we can get a fix. Outlook must be online or connected to complete this action.' All, I have seen this issue come up in a number of posts, and I am seeing the same issue at a customer site. The auto discover works (able to get configuration), but failed at last step (Logging on to the mail server) with this error message 'The connection to Microsoft Exchange is unavailable. I've tried to use autodiscover.xml file + adding entry to registry. If you're inside the company, the autodiscover works fine. The autodiscover failed to retrieve the configuration. If you try to add new email account when outside the company.

If I VPN to office, then Outlook 2010,2013,2016, can connect to exchange server.

(when setting up email choose Exchange and type in the server address)

Mobile device using Outlook App, Gmail App, phone default mail app, etc CAN connect to exchange server.

Outlook 2010,2013,2016 CANNOT connect to exchange server.

Under Outlook Anywhere, select the Connect to Microsoft Exchange using HTTP check box. Click More Settings, and then click the Connection tab. Outside the company (Internet environment) Click the File menu, click Info from the left pane, click Account Settings > Account Settings, select the Exchange account, and then click the Change button. If you want to automate this via a script, logon script or just don’t want to have to browse the registry, we can use the venerable reg.exe tool.

#Connect outlook to exchange server 2013 over internet series

I used only the public FQDN on the SSL cert, and used a series of Exchange Powershell commands to define the internal and external URLs. KB 2934750 Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013. Outlook 2010,2013,2016 can connect successfully to exchange server. Haven’t read it all the way through yet, but your article is exactly what I needed for setting this up.

Now when you add an account in Outlook 2010, it should use the information returned by 'm trying to understand how this is possible. Change the serviceBindingInformation to point to :

#Connect outlook to exchange server 2013 over internet manual

Step 5: Choose Manual setup or additional server types radio. Step 4: Enter the new Profile Name and click OK. You will see that it points to, which SBS’s internal DNS resolves to the server’s local IP address:Ĥ. Step 3: From the Mail pop-up, click Add button. On the Attributes tab, find the serviceBindingInformation attribute. Right-click on your server name and select Properties. Under Services, navigate to the Autodiscover node:ģ. In Active Directory Sites and Services, click on the fist line (Active Directory Sites and Services), then select View > Show Services Node from the menu.Ģ. So far it seems to be working-Outlook now uses the and correctly connects to Office 365. So with some trepidation, I modified the autodiscover attribute in Active Directory. This article gave me the clue I needed: in a domain environment, Outlook looks first to Active Directory to find the autodiscover location. How do I get Outlook to discover my new Office 365 account? Make sure you have an internet connection. Office 365 requires the use of autodiscover, so manual configuration is not an option. Follow these steps in Outlook 2010 and later to check and turn on the Add-in: Select the File menu. Even after configuring the public CNAME for to point to Office 365, when I tried to add an account to Outlook, it kept connecting to Exchange the SBS server. Getting Outlook to Autodiscover Office 365 For the SBS daily report, you can configure this on the SBS Reports tab: The simplest solution? Send the email to an account outside your domain, then configure that account to forward the mail back to your (now cloud-based) main account. Name resolution apparently goes through Active Directory, since there is no MX record in the internal DNS. Using Office 365 in an SBS 2008 Environment, Take 2 Getting Mail to Leave SBSĪs long as Exchange is running on your SBS server, it will greedily grab any outbound mail sent to your domain, without any respect for public MX records.

#Connect outlook to exchange server 2013 over internet update

Update AugThere is now an updated version of this article: Here are a couple gotchas that I discovered as I migrated Exchange 2007 under SBS 2008 to Office 365, and how I got around them.