Outlook 2007 SP3 can't connect to Exchange 2013

Outlok 2007 with latest hotfixes
Freshly migrated mailboxes
Gives the error
Can't open outlook-The set of folders cannot be opened
Cert has internal FQDN name. Encryption is disabled
Any pointers?

Does the certificate have the server name?
That was apparently the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/1ae67f48-d1ba-44b5-a3c7-4e9a5e955f3e/outlook-2007-cannot-connect-to-exchange-2013?forum=exchangesvrclients
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.

Similar Messages

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

Outlook 2013 can't connect to Exchange 2013 SP1

Hello,
I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain) with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
Thank you in advance,
Michael

Hi,
When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
"Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

External outlook clients can't connect to Exchange 2013

Currently running server 2012 r2 and exchange 2013 sp1...
Internally everything works fine, clients can also connect externally to owa/ecp. However when using an outlook client they are unable to connect. This is my first experience with exchange 2013 so I am at a loss. What steps should I be following to get this
working properly? Or if anyone has some suggestions to get more information I can do that as well.
Thanks!
Connecting from a mobile-phone using mail.mail.com works fine.
We are using a self-signed certificate for testing purposes..

Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Testing RPC over HTTP connectivity to server mail.mail.com
RPC over HTTP connectivity failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Attempting to resolve the host name mail.mail.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xx.x
Elapsed Time: 535 ms.
Testing TCP port 443 on host mail.mail.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 176 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 229 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.mail.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.mail.com, Issuer: CN=mail.mail.com.
Elapsed Time: 154 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.mail.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
Certificate trust is being validated.
Certificate trust validation failed.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.mail.com
A certificate chain couldn't be constructed for the certificate.
Tell me more about this issue and how to resolve it
Additional Details
The certificate chain didn't end in a trusted root. Root = CN=mail.mail.com
Elapsed Time: 33 ms.

DNS name expired, Outlook on clients can't connect to exchange anymore

Dear forum people,
We have a pro account with dyndns that kept all the dns names in check. The credit card that paid for this had expired and that wiped the DNS names we had on there. After contacting the US customer service after alot of hastle, I got a salesman on the line
that promised us that if i resubscribed for the ProAccount with a new credit card he would fix this. So I renewed but ofc the DNS names never came back. Typical me being so naïve that a salesman would take care of us after we had paid.
Problem:
The Outlook on the laptops can't connect to the exchange server.
1. I get a message box from outlook saying:
"autodiscover.(DomainName).be - information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
GOOD - the security certificate is from a trusted certifying authority
GOOD - the security certificate date is valid
NOT GOOD - the name on the security certificate is invalid or does not match the name of the site"
+'disconnected'
Question:
I have no prior knowledge of Email mechanics but i'm pretty sure I just need to reinstate the correct dns name + settings of the dns name so the connection can be made again with the exchange server. Any suggestions where I should start finding out what
the settings should be like?
§1 I'm pretty sure the emails are routed over the website which is somewhere else
§2 I did not set up the DNS names myself
§3 I have an amature IT background

Hi,
Find a related KB for your reference:
http://support.microsoft.com/kb/2772058
Thanks
Mavis
Mavis Huang
TechNet Community Support

IPhone 7 & 8 can't connect to Exchange 2013 CU5

I am getting call from users with iPhone and iPads that can't connect to our Exchange 2013 server. They get a error that the server can't be found. I can take the same account and run Microsoft online connectivity test and it passes. They don't have problem
with Outlook. Just the iPhone and iPads.
Matt Stehouwer Michigan State University

The error message I get is Exchange Account “Unable to verify account information”. This appears after the first screen that I guess you would call the autodiscovery screen if I click on that I am left on the auto discovery screen until I click cancel
I don’t advance to a screen that allows me to type the server or anything. I did the first time or two get the advanced setup screen that allowed me to type in a server but after that It wouldn’t take me to that screen again.
Looking at the cert idea.
Matt Stehouwer Michigan State University

Iphone user can't connect to Exchange 2013

Hi there,
i have Exchange 2013 on Windows 2012, PKI and certificate installed.
I have 4 users that can (must) connect to the server through iPhone. It works for all, except for ONE (the boss :-X)
I deactivate the mailbox, recreate it without import old mails. It still don't work.
Any idea?
Thanks.

Yes it's the first time on Exchange 2013.
Yes they have different OS.
The server just been installed so it never worked.
BUT I SOLVED MY PROBLEM with this article:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx It concerne Exchange 2003 and 2010 but it worked for my configuration: Windows 2012 and Exchange 2013 and no error HTTP 500.
Actually my user is member of Administrators group and the inheritance is deactivate. I activate it and it's work!
Thanks to me and thanks to you for your answers!

Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

Dear All,
I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
The 2013 environment are:-
2 X CAS server with MS NLB configured
2X MBX server with DA
Internal NLB/licent access: excas2013.int.my.domain
External access (current set on 2010 as well): webmail.my.domain
Certificate with valid subject name has been import to 2013 and 2010:
CN: webmail.mydomain
SAN: excas2013.int.my.domain
SAN: excas.int.my.domain (for 2010)
I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
the process looks good:-
Establish network connection (checked)
Searching for [email protected] server settings (checked)
Log on to server
The process stop at "Log on to server" and a windows prompt, saying:
The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicked OK, I can see:-
MS Exchange Server:
[email protected]
Mailbox:
=SMPT:[email protected]
WHen I click "Check Name", it said The name cannot be resolved.
I have no idea of what is going on. Just want some help~

I have checked the iis log:-
2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
15
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 78
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 109
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Connection beetween Exchange 2013 with outlook client 2007 SP3

Hi All,
My company reinstall exchange 2013 when the previous mailbox DB error. When I implemeted a new server. I configured step by step carefully. if we use outlook 2010 connect to exchange server, send/receive work normally. But someone, uses outlook 2007 SP3,
they have somer error. They work with "cached mode", the connection from outlook to exchange server connected normally, but mail items sometime disappear in outlook client, when i check in the OWA, the mailbox item appear on this.
I tested with "online mode", the mailbox items push into outlook.I switched to "cached mode", this items haven't in outlook. Everybody who's meet the problem, please help me the solution can resolve the problem? Many thanks.
Quoc Dao

Hi,
Would you please let me know edition information of the Windows Server? Is it a Windows Server 2012, Windows
Server 2012 R2 or other?
On current situation, please refer to following KB and check if can help you.
Sometimes e-mail messages do not appear in your
Cached mode Inbox even though they were synchronized down from your mailbox
By the way. Based on your description, this issue seems to be more related to Outlook 2007. If this issue still
exists, I suggest that you should post in
Outlook forum. I believe we will get a better assistance there.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows XP SP3 and Outlook 2010 can't connect with Exchange 2010 or Exchange 2013

XP+SP3+Outlook 2010 can't connect to Exchange 2010&2013 in the internal network without safe mode.

Hi,
Did you get any error messages?
Do you have Outlook Anywhere and autodiscovery set up properly?
Can you ping the Exchange server?
Please use Test Email AutoConfiguration
to test if the Autodiscover service is configured properly. See:
https://hosting.intermedia.net/support/kb/default.asp?id=2150
We can also use the remote connectivity analyzer to troubleshoot the issue:
https://testconnectivity.microsoft.com/
In addition, turn off your firewall and anti-virus to check the result.
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support

Unbale to install November update on Outlook 2007 SP3 for connecting to Exchange 2013

Hi
I was trying to upgrade my outlook 2007 clients for connecting to Exchange 2013 environment. First I have installed Office SP3 (kb2526086). Outlook version after that is 12.0.6607.1000. Later I tried to install nNovember 2012 update which is a
prerequisite for connecting to Exchange 2013 clients (support.microsoft.com/kb/2687404/en-us) but it shows me a message "Expected version of the product was not found on the system". No idea how to proceed now, expecting help.

I recommend that you post this in the Outlook Forum: http://social.technet.microsoft.com/Forums/en-US/outlook/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Unbale to install November update on Outlook 2007 SP3

Hi
I was trying to upgrade my outlook 2007 clients for connecting to Exchange 2013 environment. First I have installed Office SP3 (kb2526086). Outlook version after that is 12.0.6607.1000. Later I tried to install nNovember 2012 update which is a prerequisite
for connecting to Exchange 2013 clients (support.microsoft.com/kb/2687404/en-us) but it shows me a message "Expected version of the product was not found on the system". No idea how to proceed now, expecting help.

Hi,
Are you installing it manually? After installing Office 2007 SP3, please check for updates first in Windows Update, and install any available updates to your Office suite. The specific update (kb2687404) might need any other updates as
a prerequisite.
Also, please ensure Outlook is not running in compatibility mode:
Go to Program Files or Program Files (X86)>Microsoft Office>Office12, find the Outlook icon, then do a right-click on it and select ‘Properties’.
Select the ‘Compatibility’ tab then uncheck the ‘Run this program in Compatible mode for’
option. Please verify result then.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Outlook 2010 connected to Exchange 2013 prior to coexistence

I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config). I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning). Why would Outlook connect to the new
Exchange 2013 server like that? Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

Hi,
By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2007 SP3 can't connect to Exchange 2013

Similar Messages

Maybe you are looking for