Outlook(2010 and 2013) can connect to Exchange server 2013 sp1 over VPN but when connecting the network locally it's Not connecting.

We installed 2 Exchange 2013 SP1 in DAG configuration to co-exist with Exchange 2007. Everything went smoothly with the installation and configuration but our problem is  Outlook(2010 and 2013) can connect to Exchange server 2013 sp1 over VPN and its working fine BUT when connecting the network locally Outlook is Not connecting.

The OWA is working perfectly fine But when connecting the network locally outlook cannot connect to the new Exchange server 2013 sp1. The Error is The action cannot be completed. The connection to Microsoft Exchange is unavailable.Outlook must be online to complete this action.

Any help will be very appreciated...

July 15th, 2015 6:36pm

Hi Teyob,

Thank you for your question.

Did you mean outlook not connect to the Exchange in internal but it work by VPN?(if I misunderstand, please be free to let me know)

If that, we should make sure the IP address on client in internal ping Exchange without any problems(include DNS resolution), we could change the same subnet segment with VPN then check if we could connect to Exchange.

We could delete outlook profile in internal then open outlook to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 12:40am

Hi Jim, thanks for the reply..Yes outlook not connect to the Exchange in internal but it work by VPN...Client can ping the exchange.

Below are some details;

Mail2.company.com(10.1.100.10) - Exchange 2007 server SP3

Mail3.company.com(10.1.100.20) and Mail4.company.com(10.1.100.30) - Exchange 2013 server SP1

Created 2 A record in DNS Mail5.company.com with the IP address of Mail3 and Mail4 - for the DNS Round robin.

Client can ping Mail5 successfully and OWA is working fine with the address of Mail5.company.com. The 2 Exchange 2013 SP1 in DAG configuration(Failover Cluster) are working OK, if Mail3 is down Mail4 will take over.

Outlook Anywhere for Exchange 2007 SP3 - Mail2.company.com

Outlook Anywhere for Exchange 2013 SP1 - Mail5.company.com

Client email address - user1@technical.com

Client connecting internally will have this error The action cannot be completed. The connection to Microsoft Exchange is unavailable.Outlook must be online to complete this action.

We don't want client of Exchange 2007 to be affected and then we can migrate to Exchange 2013.

Your help is very much appreciated, Awaiting for your reply...

July 16th, 2015 2:12am

Hi Teyob,

Delete outlook profile and rebuild it or open outlook on other clienst to check if the issue persist. In addition, change other account to check.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 5:46am

hi jim, we had tried that one also many times..deleting the profile and creating new one,creating a new account also and using other computer but still issue persist...

regards,

July 16th, 2015 5:53am

Can you telnet to port 443 from a client machine to Exchange 2013 server? Do you also happen to have autodiscover internal records setup?
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 6:00am

Hi Teyob,

Did you user the account on Exchange 2013 or the account on account on Exchange2007 and the issue persist?

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

July 16th, 2015 6:06am

Hi Jim, the user account that has problem are the mailbox created and migrated to exchange 2013, user account from exchange 2007 are working fine they are still connected to exchange 2007.

regards

Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 7:59am

Hi Teyob,

If we create new account on Exchange 2013 , is there the same issue?

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

July 16th, 2015 9:55pm

hi jim...yes...new account and migrated account has this problem...

How about the Autodiscovery configuration?? because our domain name is different from from email address name,below is the detail;

Domain name -  .company.com

client login name - user1@company.com

client Email address - user1@technical.com

Please advice how to configure correctly the Autodiscover.

regards..

Free Windows Admin Tool Kit Click here and download it now
July 17th, 2015 5:21am

Hi Teyob,

Did the new account on Exchange 2013 connect to Exchange 2013 by VPN?

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

July 20th, 2015 10:06pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics