Outlook 2013 cannot connect to Exchange 2010 SP2 server, Outlook 2010, OWA work fine. Ideas?

After upgrading a laptop from Outlook 2010 to 2013 it can no longer connect to our Exchange 2010 SP2 environment. OWA works, Outlook 2010 works, but Outlook 2013 will not create a profile via AutoDiscover. The first two checks go, the last check
Log On To server will not.
We can take the laptop to a different network and it works fine with Outlook 2013.
What is different with Outlook 2013 where it will not connect.
Jason Meyer

Does it work when we recreate a new Outlook profile?
At this point, We high recommand that we run Microsoft Connectivity Analyzer Tool from the folloing link to check what was happening
https://testconnectivity.microsoft.com/
Cheers,
Tony Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact
[email protected]

Similar Messages

Can't connect to Exchange 2007 SP2 server

When I try and set up a new Exchange account to our internal Exchange 2007 server I get the following error message:
"The Exchange Server '<server name>' doesn't have the minimum required version installed. To use Mail with Exchange, the server must be running Update Rollup 4 for Exchange Server 2007 Service Pack 1 or later. Contact your server administrator.'
in spite of Service Pack 2 being installed on the server.
Exchange Web Services are running as expected at the URL '/EWS/Exchange.asmx'.
If anyone has suggestion on how to diagnose the exact problem I would very much appreciate the assistance.
N.

Hello,
I don't have any ideas yet but can chime in with "me too".
A customer has an Exchange 2003 SP2 server (MS Server 2003 for SBS). It has a self-signed SSL certificate that does not expire until June 2011.
One user has some species of Blackberry that can pick up his email (but not contacts or calendar) via OWA. I can see his accesses in the IIS log and they are coming from IP addresses resolving to (stuff).bise.na.blackberry.com and are not getting 404's.
Another user is trying to set up his new Blackberry via BIS. His accesses in the IIS log are coming from different IP addresses that resolve to (stuff).bis.ap.blackberry.com and these are getting 404's.
An ExpertsExchange.com article - http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_22806090.html - suggested putting the full email address into the OWA URL. This works fine in a browser but not in BIS. I still get the same error message from BIS and 404's in the IIS log.

Cannot connect my exchange 2010 from outlook outside of my LAN

I have problem connecting to my exchange 2010 server from outside of my LAN.
I have configured Outlook Anywhere and its working.
After i enter all the details it is asking again for password and once i entered the password i receive the error "The action cannot be completed. The Connection to Microsoft Exchange is unavailable etc ... "
Kindly suggest

Hi Angela,
Thanks for the support, kindly check the requested.
[PS] C:\Windows\system32>Get-ExchangeCertificate |fl
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule}
CertificateDomains : {autodiscover.mydomain.com, mydomain.com}
HasPrivateKey : True
IsSelfSigned : False
Issuer : CN=StartCom Class 1 Primary Intermediate Server CA, OU=Secure Digital Certificate Signing, O=Start
Com Ltd., C=IL
NotAfter : 2/25/2015 3:41:54 AM
NotBefore : 2/24/2014 9:47:31 AM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : 0EB79F
Services : IIS
Status : Valid
Subject : [email protected], CN=autodiscover.mydomain.com, C=KW, Description=vlkZ61QVKE36hUW5
Thumbprint : 2687AAECFD7C53DA14DDEB421D547B42A33E67BA
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule}
CertificateDomains : {*.mydomain.com}
HasPrivateKey : True
IsSelfSigned : True
Issuer : C=KW, S=Kuwait, L=Kuwait, O=mydomain.com, OU=IT, CN=*.mydomain.com
NotAfter : 2/11/2015 3:58:45 PM
NotBefore : 2/11/2014 3:38:45 PM
PublicKeySize : 2048
RootCAType : None
SerialNumber : 6DFCB427D57AE58746B5DF8B070E6455
Services : None
Status : Valid
Subject : C=KW, S=Kuwait, L=Kuwait, O=mydomain.com, OU=IT, CN=*.mydomain.com
Thumbprint : 4A90303EBFA71BB73928E9BFB9FD5D129EEC9270
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
essRule}
CertificateDomains : {exchange, exchange.mydomain.com}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=exchange
NotAfter : 2/11/2019 6:30:52 AM
NotBefore : 2/11/2014 6:30:52 AM
PublicKeySize : 2048
RootCAType : None
SerialNumber : 7BBA32A69E5DC2B2404406700225B006
Services : IMAP, POP, SMTP
Status : Valid
Subject : CN=exchange
Thumbprint : 565B3D127A98DB2D25FAE71864E58B427F17FC3C
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-EXCHANGE}
HasPrivateKey : True
IsSelfSigned : True
Issuer : CN=WMSvc-EXCHANGE
NotAfter : 2/8/2024 3:44:28 PM
NotBefore : 2/10/2014 3:44:28 PM
PublicKeySize : 2048
RootCAType : Registry
SerialNumber : 168EC4DED2C01B874C8BD6F16E231229
Services : None
Status : Valid
Subject : CN=WMSvc-EXCHANGE
Thumbprint : 736EF13159F0F851EFCC20709C00AE60D5A54C94
Thanks

TS1398 I still can't update my apps. Continues to say cannot connect to ITunes store. Everything else using Internet works fine. How can I fix this?

I need help. I cant update my apps because of I cannot connect to iTunes store. I have tried all suggestions with no success.

Ok, I found a solution that worked for me when trying to connect to the iTunes store by tapping the "update" button in the "App Store" app on my iPad 2. Before the solution was implemented I'd always get the error message "cannot connect to iTunes store". Once the solution was implemented I now can connect to iTunes using the "update" button in the "App Store" app and I get the normal message "All apps are up to date". The solution is this: go into Settings, then General, then scroll to the bottom where it says Date and Time. Tap Date and Time and then turn OFF Set Automatically. When you do that a new option will be added that says Set Date and Time. Tap it. You'll now get a drop down feature. Set the Date AHEAD 2 YEARS. The Time you can leave alone.
Once you do that you might get a bunch of reminders and messages that your apps and stuff haven't been updated in two years. Click cancel or close on each of those messages or reminders. Now go back into Settings, General, Date and Time, and turn Set Automatically back to ON. Reboot your iPad. Open the App Store app again and go to the Update button. It might ask you to log back in to your iTunes account. It should now work. If not, close the App Store app completely and open again and try the update button. Hope this helps.

Unity cannot connect to Exchange 2010 mailbox

Unity 8 with Es9 and call manager: System version: 8.5.1.11900-21.
Out of nowhere one of the mailboxes has this issue:
System version: 8.5.1.11900-21
This message has the following recipients : ([vm3131] ). The recipient mailboxes may be disabled or inaccessible, Cisco Unity may be having trouble connecting with the partner server, or the Cisco Unity messaging component may not be properly configured.
Any ideas?
No problems with other mailboxes.

Hello Bart -
Take at look at this recent post from my Cisco friend Brad Mangnani and see if that user is hidden in AD -
https://supportforums.cisco.com/message/3301386
Sincerely, Ginger

My IPad 2 also will not connect to ITunes for updates and purchased apps. It shows Waiting for several minutes then says it cannot connect to ITunes. All other wifi functions are working fine on it.

I see this is happening to a lot of folks today. Has anyone found a solution?

It is not properly connected to the network.
Make sure location is set correctly
DNS should be on auto (settings - general - network)
Try ethernet
Signal strength on device won't account for issues, you would need a network report from istumbler, netstumbler or similar. This will show accurate signal strength along with noise and nearby networks

It says I cannot connect to iTunes, but my internet and everything is working fine

.

1. Make sure iPad is using the latest software
2. Settings>General>Date and Time>Set Automatically>On
3. Make sure Time Zone is correct
4. Reset iPad. Hold the Sleep and Home button down until you see the Apple Logo.

Outlook 2013 cannot connect to local Exchange 2013 server

Server name EXCHANGE: is Domain controller for (domainname.local), DNS server and Exchange 2013
Has UCC CA cert successfully installed for (exchange.domainname.com)
External Outlook connections, Web Outlook and autodiscover work fine.
local DNS points autodiscover.domain.com & exchange.domainname.com to internal IP
I have used the above configuration many time for Exch2010/Outlook 2010 and it works great.
PROBLEM: Outlook 2013 clients on a local domain member autoconfigure (through autodiscover) but report a certificate error that the names do not match. When I force the acceptance for the cert error the outlook13 account setups with an exchange server
of "BIG LONG GUID"@domainname.com which cannot resolve and outlook fails.
Please help..

Hi ,
I have recently installed the exchnage 2013 as follow
one CAS and Two mail box DAG
so I was facing similier issue outlook clients were not able not see the CAS
so here are the magic solution :
1-created SRV recored for autodiscover same as acbrown2010 done
above in his reply
2-created
A record for autodiscover and the IP same as CAS IP
3-created
an internal Certificate in CAS server "create a new certificate request " and
include all names such CAS , MB's , Autodiscover this step to avoid the warning message during outlook setup because self sign certificates in ex2013 not helping
after that I have tested the outlook and was working fine NO GUID and NO certificates warning

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

No calendar connection for Exchange 2010 + Outlook 2013

My environment is this:
Running Outlook 2013 (as part of Office 2013 Suite) connecting to Exchange Server 2010
Both cached and non-cached modes
Connecting using RPC
With both existing profile for last 1yr+ and with a new profile
Outlook v 15.0.4649.1001
The issue I'm having is a room/resource calendar that I was once able to see I can't anymore.
Running Outlook 2010 as the same user from a different computer works fine.
OWA works as well.
Other calendars work
Running Outlook 2013 vs 15.0.4420.1017 also works on a different computer!!!
So this seems to be an issue with my particular version of Outlook, and I did read where a security update seems to have gotten in the way (regression test lately?) but a December patch of 2013 was supposed to fix that. I didn't specifically install the
patch, rather I downloaded from my vendor the latest available version they had.
So is there a patch that will work for me. The only one I've come across tells me it isn't for my machine.
Thanks,
Joe

Hi,
According to your description and test, I understand that the room/resource calendar is invisible in Outlook.
How about changing another user to log on your Outlook?
How about the same version of Outlook on another computer?
Please try to run Outlook under safe mode to avoid some AVs and add-ins.
Please try to re-create profile for testing.
If all method above doesn’t work, please re-install Outlook.
Best Regards,
Allen Wang

Lync 2013 on Windows Phone 8 cannot connect to Exchange via TMG

Hi,
I've found that the latest Lync 2013 client on WP8 cannot connect to our Exchange Server 2010 via TMG and the problem is related to autodiscovery. Based on detailed log analysis the symptom is the following:
1. The client is sending a request:
GET
https://autodiscover.neostratus.com/autodiscover/autodiscover.xml
2. It gets a TMG logon form and then tries to POST here:
POST
https://autodiscover.neostratus.com/cookieauth.dll?getlogon?curl=z2fautodiscoverz2fautodiscover.xml&reason=0&formdir=9
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
<Request><EMailAddress>[email protected]</EMailAddress>
<AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>
</Request></Autodiscover>
</SentRequest>
The URL is wrong and it fails of course. This is the situation with Lync credentials and manually configured Exchange credentials as well.
Other clients (PC, iOS) can connect fine and all test tools confirm that our autodiscovery setup is correct. I can POST the above XML using basic authentication to the correct URL and get a correct response. And the same autodiscovery process works fine
when setting up an email account on the same WP8 device.
Is this a known WP8 Lync 2013 client bug and is there a workaround?
BR,
Andras

Hi,
The lync client should be able to sing in Lync Server and just lost calendar information if Lync client cannot connect to Exchange. Please double check if the device is able to connect to the EWS URL.
Kent Huang
TechNet Community Support

Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

Hi
We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
I'm now testing with a few test users I've migrated from 2007 to 2013.
Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
When I start Outlook, I get the error Unable to open the default mail folders
When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
Thanks for any help you could provide
Martin

Changed the
ExternalClientAuthenticationMethod for the 2007 server.
Output for Get-OutlookAnywhere | fl *method*
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
asking for credentials.
If I dig further and try to manually configure server settings:
If I specify the Exchange 2013 server and try a 'Check
Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
If I specify the Exchange 2007 server and try a 'Check
Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
Any other thoughts on this issue?
Thanks,
Martin

Outlook 2010 won't connect to exchange 2010 - logon box appears

Users can't connect to Exchange server from outlook 2010. The domain\user and password boxes keep popping up and will not accept the details. It ends with "the connection to exchange is unavailable. Outlook needs to be online to perform
this action"
I've searched high and low for an answer and none work. Anyone any ideas?
Exchange is behind Threat Management Gateway 2010, with applicable rules setup. Strangeley, Outlook Web Access works fine with no problems what so ever.
Thanks in advance
Andy

Ok. Done some reading and made some adjustments but still pretty much the same. Microsofts Exchange analyser tool come up with the folowing errors and does indeed pinpoint it down to the autodiscover service. The srv record for the autodiscover
service - should that be on my own internal DNS or on my web host DNS?
The results of the connectivity test are below:
Testing RPC/HTTP connectivity.
The RPC/HTTP test failed.
Test Steps
ExRCA is attempting to test Autodiscover for [email protected].
Testing Autodiscover failed.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Test Steps
Attempting to test potential Autodiscover URL https://owa.optima-ws.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name owa.optima-ws.co.uk in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 78.33.247.168
Testing TCP port 443 on host owa.optima-ws.co.uk to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
ExRCA is attempting to obtain the SSL certificate from remote server owa.optima-ws.co.uk on port 443.
ExRCA successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=owa.optima-ws.co.uk, OU=Domain Control Validated - GeoTrust(R) SSL Trial, OU=www.geotrust.com/resources/cps, OU=GT52908676, SERIALNUMBER=OyRDVCpo58GRaYQL5CORIFnTYn4Odw9G, Issuer: CN=GeoTrust DV SSL CA, OU=Domain Validated
SSL, O=GeoTrust Inc., C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name owa.optima-ws.co.uk was found in the Certificate Subject Common name.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
ExRCA is attempting to build certificate chains for certificate CN=owa.optima-ws.co.uk, OU=Domain Control Validated - GeoTrust(R) SSL Trial, OU=www.geotrust.com/resources/cps, OU=GT52908676, SERIALNUMBER=OyRDVCpo58GRaYQL5CORIFnTYn4Odw9G.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=GeoTrust Global CA, O=GeoTrust Inc., C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/24/2012 7:35:43 PM, NotAfter = 8/25/2012 12:31:49 PM
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Test Steps
ExRCA is attempting to retrieve an XML Autodiscover response from URL https://owa.optima-ws.co.uk/AutoDiscover/AutoDiscover.xml for user [email protected].
ExRCA failed to obtain an Autodiscover XML response.
Additional Details
An HTTP 500 response was returned from Unknown.
Attempting to test potential Autodiscover URL https://autodiscover.owa.optima-ws.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name autodiscover.owa.optima-ws.co.uk in DNS.
The host name couldn't be resolved.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Host autodiscover.owa.optima-ws.co.uk couldn't be resolved in DNS InfoDomainNonexistent.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Test Steps
Attempting to resolve the host name autodiscover.owa.optima-ws.co.uk in DNS.
The host name couldn't be resolved.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl02_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Host autodiscover.owa.optima-ws.co.uk couldn't be resolved in DNS InfoDomainNonexistent.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.owa.optima-ws.co.uk in DNS.
The Autodiscover SRV record wasn't found in DNS.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl03_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>

Can't connect to Exchange 2003 SP2 using BIS

Hi,
I'm a network administrator for a small company. We have a user with a Blackberry 8830, and they'd like to access their Exchange account from the device. We're running Exchange 2003 SP2.
I attempted to set this up on the Blackberry and got the following error:
"Cannot connect to email server or invalid server name. Please verify the Outlook Web Access URL. If the error persists, contact antarcticadigital.com (your email provider)."
The user received an email with the following info:
Your attempt to configure the BlackBerry Internet Service to deliver mail to your BlackBerry device from this email account was unsuccessful. This email provides instructions to help with the email account set up.
You submitted the following information:
Account Type:
Outlook Web Access
Email Address:
[email protected]
User Name:
connectusdirect\person
Password:
****** (For security the password is not displayed.)
Mail Server:
https://mail.xyz.com/exchange/
[removed personal information]
For historical reasons, our Windows domain name is connectusdirect, while the email domain is different (antarcticadigital.com).
I've set this up before when I had a blackberry of my own, and it worked OK for me - so I'm not sure why we're having a problem with this user's account.
On our mail server, I'm seeing the following in the IIS logs for the OWA site. These are coming from a RIM-controlled IP:
2010-05-03 19:52:02 W3SVC1 192.168.3.23 PROPFIND /exchange/jrebak - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 2 2148074254 357 410 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 PROPFIND /exchange/jrebak - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 1 0 345 456 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 PROPFIND /exchange/jrebak - 80 CONNECTUSDIRECT\jrebak 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 404 0 0 387 640 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 POST /EWS/Exchange.asmx - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 404 0 0 1753 832 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 POST /exchange - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 2 2148074254 376 823 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 POST /exchange - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 1 0 345 874 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 POST /exchange - 80 CONNECTUSDIRECT\jrebak 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 404 0 0 1848 1058 93
2010-05-03 19:52:02 W3SVC1 192.168.3.23 GET /exchange - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 2 2148074254 357 148 78
2010-05-03 19:52:02 W3SVC1 192.168.3.23 GET /exchange - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 1 0 345 194 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange - 80 CONNECTUSDIRECT\jrebak 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 302 0 0 383 378 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange/logon.asp - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 2 2148074254 357 158 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange/logon.asp - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 401 1 0 345 204 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange/logon.asp - 80 CONNECTUSDIRECT\jrebak 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) - - mail.antarcticadigital.com 404 0 0 1848 388 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange/ - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+4.0) - - mail.antarcticadigital.com 401 2 2148074254 357 219 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange/ - 80 - 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+4.0) - - mail.antarcticadigital.com 401 1 0 345 265 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 GET /exchange/ - 80 CONNECTUSDIRECT\jrebak 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+4.0) - - mail.antarcticadigital.com 200 0 0 1485 449 78
2010-05-03 19:52:03 W3SVC1 192.168.3.23 PROPFIND /exchange/jrebak/ - 80 CONNECTUSDIRECT\jrebak 67.223.64.111 Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+4.0) sessionid=af524a8e-7c18-4926-a10e-803bf5cc70f8:0x0 - mail.antarcticadigital.com 404 0 0 387 472 78
Does anyone have any ideas?
Thanks,
Richard

Hello,
I don't have any ideas yet but can chime in with "me too".
A customer has an Exchange 2003 SP2 server (MS Server 2003 for SBS). It has a self-signed SSL certificate that does not expire until June 2011.
One user has some species of Blackberry that can pick up his email (but not contacts or calendar) via OWA. I can see his accesses in the IIS log and they are coming from IP addresses resolving to (stuff).bise.na.blackberry.com and are not getting 404's.
Another user is trying to set up his new Blackberry via BIS. His accesses in the IIS log are coming from different IP addresses that resolve to (stuff).bis.ap.blackberry.com and these are getting 404's.
An ExpertsExchange.com article - http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_22806090.html - suggested putting the full email address into the OWA URL. This works fine in a browser but not in BIS. I still get the same error message from BIS and 404's in the IIS log.

Exchange 2010 OWA usage in Exchange 2013

Hi,
I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
Before Migration we want below things to keep in mind...
1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
2. Can i use my Existing Exchange certificate to get the above goal done ?
3. What will be the steps and pre-requsite to achieve the Goal ?
An Early reply would be appreciated !!
Amit

Hi Amit
First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
Configure external DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
Ensure that you are having a seperate name for CAS array from external ews url
Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
Authentication for OUtlook Anywhere should be - NTLM
for OWA exchange 2010 - FBA and windows
Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users
You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
Apply a new certificate with all the required site names included in Exchange 2013 CAS.
Whats more you can refer my blog as well
http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
Cheers :)
Remember to 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 Check out my latest blog posts on http://exchangequery.com

Outlook 2013 cannot connect to Exchange 2010 SP2 server, Outlook 2010, OWA work fine. Ideas?

Similar Messages

Maybe you are looking for