[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 653
  • Last Modified:

Outlook on Windows 7 Phone

I recently bought a windows 7 phone, the htc trophy. I have not had a problem with the phone up until today. I have been trying to set up my outlook 2007 account on my cell phone and cannot get it to work for the life of me. My tech support for the office could not either. I have the domain name, server name, everything and it keeps saying that it cannot sync. We tried pointing it to the IP address, rather than the server address and it didn't like that. I got error code 80072F06. Please help. It's a little ironic that my windows phone won't sync with my outlook account.
0
mkennelly0418
Asked:
mkennelly0418
  • 6
  • 6
3 Solutions
 
Alan HardistyCommented:
Assuming you have an Exchange server at the office - what version is it?

Alan
0
 
mkennelly0418Author Commented:
exchange server 2007
0
 
Alan HardistyCommented:
Okay - thanks.

Please visit https://testexchangeconnectivity.com and run the Exchange Activesync Autodiscover test and report back what the results are please.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mkennelly0418Author Commented:
Attempting the Autodiscover and Exchange ActiveSync test (if requested).
 Testing of Autodiscover for Exchange ActiveSync 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://domain.com/AutoDiscover/AutoDiscover.xml
 Testing of this potential Autodiscover URL failed.
 Test Steps
 Attempting to resolve the host name domain.com in DNS.
 The host name resolved successfully.
 Additional Details
 IP addresses returned: 208.110.xxx.xxx

Testing TCP port 443 on host domain.com to ensure it's listening and open.
 The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
 The SSL certificate failed one or more certificate validation checks.
 Test Steps
 ExRCA is attempting to obtain the SSL certificate from remote server domain.com on port 443.
 ExRCA wasn't able to obtain the remote SSL certificate.
 Additional Details
 The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.





Attempting to test potential Autodiscover URL https://autodiscover.domain.com/AutoDiscover/AutoDiscover.xml
 Testing of this potential Autodiscover URL failed.
 Test Steps
 Attempting to resolve the host name autodiscover.domain.com in DNS.
 The host name couldn't be resolved.
  Tell me more about this issue and how to resolve it
 Additional Details
 Host autodiscover.domain.com 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.domain.com in DNS.
 The host name couldn't be resolved.
  Tell me more about this issue and how to resolve it
 Additional Details
 Host autodiscover.domain.com 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.domain.com in DNS.
 The Autodiscover SRV record wasn't found in DNS.
  Tell me more about this issue and how to resolve it
0
 
mkennelly0418Author Commented:
that is not the correct IP address, or the server address either
0
 
Alan HardistyCommented:
Okay - are you using the correct FQDN for the server?  It should be something like mail.domain.com not just domain.com.

What do you use to access OWA?
0
 
mkennelly0418Author Commented:
yes i do, it is remote.____.com
0
 
mkennelly0418Author Commented:
yes it is an owa
0
 
Alan HardistyCommented:
Try that instead of domain.com and see if that makes the results happier.

I will tidy up your earlier post to obscure the domain name.

Alan
0
 
Alan HardistyCommented:
What doesn't look encouraging is the lack of autodiscover.domain.com - which will be needed with Exchange 2007 to make Exchange happy.

Your IT department needs to create a A record in your domains DNS records (external - not Internal) called Autodiscover and point that to the IP Address of your Exchange Server.

They also need an SSL certificate (SAN / UCC - Multi Name) with the following names included:

remote.domain.com
autodiscover.domain.com
internalservername.internaldomainname.local
internalservername
0
 
mkennelly0418Author Commented:
thank you, about the post. I have tried that. I just handed my phone to someone who figured it out though- my domain name i had been typing in all caps because that is how our server shows it. They typed it in lower case, only change, and it worked. crazy. Thank you for you're help though.
0
 
Alan HardistyCommented:
Okay - a fix is a fix - not seen that one before though!

You are welcome - better luck next time.

Please accept your last comment as the solution.

Alan
0
 
Mike_BickfordCommented:
This problem has been solved multiple times before.  The issue here is that some windows phones do a verification that the CN on the certificate matches the CN of the server address you enter in the setup.   On a self signed certificate, it won't match unless your public URL uses a host name that matches the CN of the mail server.
For example:
You use a vanilla name for the external URL of your mail server.... mail.xyzcorp.com  (CN=mail, DC=xyzcorp, DC=com)

The real FQDN of the  host is  Exchange.xyz.local.( CN=Exchange, DC=xyzcorp,DC=Local)  A self signed certificate will say it is from CN=Exchange, DC=xyzcorp, DC=local..  

The phone will check and fail the connection because the CN are not the same.   Interestingly enough it doesn't give a damn if the DC match or not.

To solve the problem, put an A record on the name server that matches the CN of the server, and setup the phone to look for it.  
S
Alternately issue a certificate that matches the vanilla name of the connection and install it on the phone.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now