Outlook 2007 cannot connect to Mailbox after migrating to Exchange 2013
Greetings Experts,
I am in the phase of migrating my Exchange 2010 Server to Exchange 2013.
Some mailboxes are currently to Exch 2010 and some have been migrated to Exch 2013.
Using Outlook 2007 and for Mailboxes that now live on Exch 2013:
- I add a new E-mail Service and select the Microsoft Exchange ‘’profile”
-I enter the Exch Server 2013 IP address
-I enter the user name and when I click check (in order to find the username)
I receive the following message:
“The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.”
Please note that following the above procedure for mailboxes that are still on Exch 2010,
the username is resolved successfully and the outlook connects to the mailbox.
Please also note that I can successfully connect to the Exch 2013 Mailboxes via OWA, IMAP and POP3.
What am I missing here?
I am in the phase of migrating my Exchange 2010 Server to Exchange 2013.
Some mailboxes are currently to Exch 2010 and some have been migrated to Exch 2013.
Using Outlook 2007 and for Mailboxes that now live on Exch 2013:
- I add a new E-mail Service and select the Microsoft Exchange ‘’profile”
-I enter the Exch Server 2013 IP address
-I enter the user name and when I click check (in order to find the username)
I receive the following message:
“The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.”
Please note that following the above procedure for mailboxes that are still on Exch 2010,
the username is resolved successfully and the outlook connects to the mailbox.
Please also note that I can successfully connect to the Exch 2013 Mailboxes via OWA, IMAP and POP3.
What am I missing here?
Are any mailboxes accessible on exchange 2013?
Can you confirm the mailboxes have been moved accross correctly into exchange 2013? login to the emc and check.
It sounds like the mailboxes are not moved, why would they still resolve on the 2010 server if they have been moved to 2013?
Can you confirm the mailboxes have been moved accross correctly into exchange 2013? login to the emc and check.
It sounds like the mailboxes are not moved, why would they still resolve on the 2010 server if they have been moved to 2013?
ASKER
Dear Mas,
Where should I ckeck the if the autodiscover and common name are pointed to the correct Exchange?
Could you please provide me the steps required?
Thanks in advance
Where should I ckeck the if the autodiscover and common name are pointed to the correct Exchange?
Could you please provide me the steps required?
Thanks in advance
ASKER
Dear Mark Bill,
The Mailboxes that I have chosen to be migrated are moved successfully.
The Mailboxes that can be resolved from Exch 2010, are the mailboxes
that are not migrated yet. Therefore they reside to Exch 2010.
For Mailboxes that reside to Exch 2013, can be accessed via OWA/POP and IMAP
but NOT via Outlook.
The Mailboxes that I have chosen to be migrated are moved successfully.
The Mailboxes that can be resolved from Exch 2010, are the mailboxes
that are not migrated yet. Therefore they reside to Exch 2010.
For Mailboxes that reside to Exch 2013, can be accessed via OWA/POP and IMAP
but NOT via Outlook.
Can you login to any mailbox on Exchange 2013 server?
Who did the migration?
Who did the migration?
ASKER
Dear Mark Bill,
As per my above commnet I can connect to the Mailboxes that live on Exch 2013
via OWA , Pop3 and Imap.
The Outlook 2007 can connect to these mailboxes via pop3 account but not
by selecting the Microsoft Exchange option.
As per my above commnet I can connect to the Mailboxes that live on Exch 2013
via OWA , Pop3 and Imap.
The Outlook 2007 can connect to these mailboxes via pop3 account but not
by selecting the Microsoft Exchange option.
ASKER
In addition to the above messages please be advised that
the Autodiscover exists to Exch 2010 and Exch 2013 as well.
Is it possible to set the default Autodiscovery Server?
(I am assume that during outlook mailbox setup the outlook
search the username using the Autodiscovery of the Old 2010 Exch)
the Autodiscover exists to Exch 2010 and Exch 2013 as well.
Is it possible to set the default Autodiscovery Server?
(I am assume that during outlook mailbox setup the outlook
search the username using the Autodiscovery of the Old 2010 Exch)
Did you point autodiscover.emaildomain.c
If not please do change it.
Did you point your common name to Exchange 2013 IP
If not please do change it.
If not please do change it.
Did you point your common name to Exchange 2013 IP
If not please do change it.
ASKER
Dear Mas,
The IP of Exchange 2010 is the 192.168.1.10 and the DNS is the ex2010.mydomain.com
The IP of Exchange 2013 is the 192.168.1.13 and the DNS is the ex2013.mydomain.com
For a mailbox that resides now on Exchange 2013:
On outlook I select the option "manually configure settings"
Under "Microsoft Exchange Server Field" if I enter the IP of Exch 2010 -> 192.168.1.10
The IP changes to the DNS of Exchange 2013, ex2013.mydomain.com
and the mailbox is connected.
Repeating the above steps using as the IP of Exch2013 192.168.13 and
I receive the message “The connection to Microsoft Exchange is unavailable......."
Is the common name and autodiscover responsible for the above mentioned error?
If yes, where should I navigate in order to change common name and pointer of autodiscover?
The IP of Exchange 2010 is the 192.168.1.10 and the DNS is the ex2010.mydomain.com
The IP of Exchange 2013 is the 192.168.1.13 and the DNS is the ex2013.mydomain.com
For a mailbox that resides now on Exchange 2013:
On outlook I select the option "manually configure settings"
Under "Microsoft Exchange Server Field" if I enter the IP of Exch 2010 -> 192.168.1.10
The IP changes to the DNS of Exchange 2013, ex2013.mydomain.com
and the mailbox is connected.
Repeating the above steps using as the IP of Exch2013 192.168.13 and
I receive the message “The connection to Microsoft Exchange is unavailable......."
Is the common name and autodiscover responsible for the above mentioned error?
If yes, where should I navigate in order to change common name and pointer of autodiscover?
ASKER
In addition I have created on my DNS server the following:
1)An "Alias (CNAME)" with Alias name: Autodiscover and FQDN the FQDN of the Exchange 2013 Server
which is the ex2013.mydomain.com
2)A "Service Location (SRV)" with the name: _autodiscover , domain: mydomain.com , port number: 443 and host offering this service: autodiscover.mydomain.com.
Now, when I ping the "autodiscover.mydomain.com
But still I have the problem connecting to Outlook as per my previous post...Any Help Please?
1)An "Alias (CNAME)" with Alias name: Autodiscover and FQDN the FQDN of the Exchange 2013 Server
which is the ex2013.mydomain.com
2)A "Service Location (SRV)" with the name: _autodiscover , domain: mydomain.com , port number: 443 and host offering this service: autodiscover.mydomain.com.
Now, when I ping the "autodiscover.mydomain.com
But still I have the problem connecting to Outlook as per my previous post...Any Help Please?
ASKER
To sum up:
1) The CN of the Exchange's 2013 Self-signed certificate is now pointing to Exchange 2013 Server
2) The Autodiscover now resolves the IP of Exchange's 2013 Server
for a mailbox that is migrated/resides to Exchange 2013:
3) If I let Outlook 2007 to automatically configure settings, the mailbox is connected successfully
(the only alert that I receive is that the security sertificate was issued by a not trusted company)
4) If I manually configure settings the Exchange 2013 server is not resolved neither by entering the
IP address nor by the DNS name.
(I have found that in case I enter the IP of Exchange 2010 and click "check name" button, the IP changes to the DNS of Exchange 2013 and the mailbox is connected.) But why??
1) The CN of the Exchange's 2013 Self-signed certificate is now pointing to Exchange 2013 Server
2) The Autodiscover now resolves the IP of Exchange's 2013 Server
for a mailbox that is migrated/resides to Exchange 2013:
3) If I let Outlook 2007 to automatically configure settings, the mailbox is connected successfully
(the only alert that I receive is that the security sertificate was issued by a not trusted company)
4) If I manually configure settings the Exchange 2013 server is not resolved neither by entering the
IP address nor by the DNS name.
(I have found that in case I enter the IP of Exchange 2010 and click "check name" button, the IP changes to the DNS of Exchange 2013 and the mailbox is connected.) But why??
-->(the only alert that I receive is that the security sertificate was issued by a not trusted company)
This is because of the IIS not enabled on the 3rd party certificate. Instead it is enabled on self signed certificate
This is because of the IIS not enabled on the 3rd party certificate. Instead it is enabled on self signed certificate
ASKER
That's true. I will buy a certificate the following days.
But what about 4) ???
But what about 4) ???
ASKER
I have tried:
- To shutdown the Exch 2010 in order to “push” outlook to connect and resolve the IP of Exch 2013, with no luck
- I have pointed the CN of Exch 2013 to the IP of this Server
- I have created an autodiscover entry and it is now resolves the IP of Exch 2013
The Exch 2010 Server was also a Primary DC/DNS server. I have transferred the DC and FSMO roles to a new DC.
The Exch 2010 Server has now only the Global Catalog.
Regarding Global Catalog & Exchange I have found the following resolution and I am wondering if this solves also my connection problems:
Cannot connect to or resolve Exchange Server name
- To shutdown the Exch 2010 in order to “push” outlook to connect and resolve the IP of Exch 2013, with no luck
- I have pointed the CN of Exch 2013 to the IP of this Server
- I have created an autodiscover entry and it is now resolves the IP of Exch 2013
The Exch 2010 Server was also a Primary DC/DNS server. I have transferred the DC and FSMO roles to a new DC.
The Exch 2010 Server has now only the Global Catalog.
Regarding Global Catalog & Exchange I have found the following resolution and I am wondering if this solves also my connection problems:
Cannot connect to or resolve Exchange Server name
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
-
Did you point your autodiscover and common name to Exchange 2013 IP?