none
Iphone 4s fails to setup with exchange

    Question

  • I run exchange server 2007 enterprise edition sp3

    Just got my iphone 4s when I try to setup the exchange email account I get unable to verify account information

    I type in my email address

    domain

    username

    password

     

    my user name has spaces example joe r smith

    I tried joersmith

    still get the same error

     

    I have autodiscovery on

    not sure how to test if it is working or not

    I can access my exchange server using owa no problem with both accounts

    was on the phone with verizon and we setup exchange account on there test site so the iphone is ok

    any ideas on what I can check

    Please help

    Thanks in adavnce

     

    Tom


    Thomas R Grassi Jr
    Sunday, October 16, 2011 11:10 PM

Answers

  • Got it to work

    Issue was that WIFI was turned on once I turned off the WIFI feature I was able to connect

    Also you must add the domain name it is not optional as the setup claims it is required

    Thanks for all your help

    Tom


    Thomas R Grassi Jr
    • Marked as answer by TRGOneCare Tuesday, October 18, 2011 4:14 PM
    Tuesday, October 18, 2011 4:14 PM

All replies

  • Hi TRGOneCare,

    Try to verify with:
    https://www.testexchangeconnectivity.com/

    I installed the new fw on my iPhone4 and everything is fine...


    __________________
    Viele Grüße
    Christian

    Monday, October 17, 2011 11:54 AM
  • I ran that and it was successfull here are the results

     

     

     

    Attempting the Autodiscover and Exchange ActiveSync test (if requested).

    Autodiscover was successfully tested for Exchange ActiveSync.
    Test Steps
    Attempting each method of contacting the Autodiscover service.

    The Autodiscover service was tested successfully.
    Test Steps
    Attempting to test potential Autodiscover URL https://tgcsnet.com/AutoDiscover/AutoDiscover.xml

    Testing of the Autodiscover URL was successful.
    Test Steps
    Attempting to resolve the host name tgcsnet.com in DNS.

    The host name resolved successfully.
    Additional Details

    IP addresses returned: 72.88.223.20

    Testing TCP port 443 on host tgcsnet.com 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 tgcsnet.com on port 443. 

    ExRCA successfully obtained the remote SSL certificate.
    Additional Details

    Remote Certificate Subject: CN=webmail.tgcsnet.com, OU=Domain Control Validated, O=webmail.tgcsnet.com, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.

    Validating the certificate name. 

    The certificate name was validated successfully.
    Additional Details

    Host name tgcsnet.com was found in the Certificate Subject Alternative Name entry.

    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=webmail.tgcsnet.com, OU=Domain Control Validated, O=webmail.tgcsnet.com. 

    One or more certificate chains were constructed successfully.
    Additional Details

    A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.

    Analyzing the certificate chains for compatibility problems with versions of Windows.

    No Windows compatibility problems were identified.

    Additional Details

    The certificate chain has been validated up to a trusted root. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network.

    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 = 9/26/2010 12:39:45 AM, NotAfter = 9/18/2015 2:10:28 AM

    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.

    ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST.

    Test Steps

    ExRCA is attempting to retrieve an XML Autodiscover response from URL https://tgcsnet.com/AutoDiscover/AutoDiscover.xml for user thomasrgrassijr@tgcsnet.com

    The Autodiscover XML response was successfully retrieved.
    Additional Details

    Autodiscover Account Settings
    XML response:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
     <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
     <Culture>en:en</Culture>
     <User>
     <DisplayName>Thomas R. Grassi Jr</DisplayName>
     <EMailAddress>ThomasRGrassiJr@tgcsnet.com</EMailAddress>
     </User>
     <Action>
     <Settings>
     <Server>
     <Type>MobileSync</Type>
     <Url>https://webmail.tgcsnet.com/microsoft-server-activesync</Url>
     <Name>https://webmail.tgcsnet.com/microsoft-server-activesync</Name>
     </Server>
     </Settings>
     </Action>
     </Response>
    </Autodiscover>

     

    ExRCA is testing Exchange ActiveSync.
    Exchange ActiveSync was tested successfully.
    Test Steps
    Atempting the Autodiscover and Exchange ActiveSync test (if requested).
    Autodiscover was successfully tested for Exchange ActiveSync.
    Test Steps
    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.
    Test Steps
    Attempting to test potential Autodiscover URL https://tgcsnet.com/AutoDiscover/AutoDiscover.xml
    Testing of the Autodiscover URL was successful.
    Test Steps
    Attempting to resolve the host name tgcsnet.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 72.88.223.20
    Testing TCP port 443 on host tgcsnet.com 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 tgcsnet.com on port 443.
    ExRCA successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=webmail.tgcsnet.com, OU=Domain Control Validated, O=webmail.tgcsnet.com, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name tgcsnet.com was found in the Certificate Subject Alternative Name entry.
    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=webmail.tgcsnet.com, OU=Domain Control Validated, O=webmail.tgcsnet.com.
    One or more certificate chains were constructed successfully.
    Additional Details
    A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
    Analyzing the certificate chains for compatibility problems with versions of Windows.
    No Windows compatibility problems were identified.
    Additional Details
    The certificate chain has been validated up to a trusted root. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network.
    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 = 9/26/2010 12:39:45 AM, NotAfter = 9/18/2015 2:10:28 AM
    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.
    ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST.
    Test Steps
    ExRCA is attempting to retrieve an XML Autodiscover response from URL https://tgcsnet.com/AutoDiscover/AutoDiscover.xml for user thomasrgrassijr@tgcsnet.com.
    The Autodiscover XML response was successfully retrieved.
    Additional Details
    Autodiscover Account Settings
    XML response:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
     <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
     <Culture>en:en</Culture>
     <User>
     <DisplayName>Thomas R. Grassi Jr</DisplayName>
     <EMailAddress>ThomasRGrassiJr@tgcsnet.com</EMailAddress>
     </User>
     <Action>
     <Settings>
     <Server>
     <Type>MobileSync</Type>
     <Url>https://webmail.tgcsnet.com/microsoft-server-activesync</Url>
     <Name>https://webmail.tgcsnet.com/microsoft-server-activesync</Name>
     </Server>
     </Settings>
     </Action>
     </Response>
    </Autodiscover>
    Validating Exchange ActiveSync settings.
    Exchange ActiveSync URL https://webmail.tgcsnet.com/microsoft-server-activesync was validated successfully.
    Attempting to resolve the host name webmail.tgcsnet.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 72.88.223.20
    Testing TCP port 443 on host webmail.tgcsnet.com 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 webmail.tgcsnet.com on port 443.
    ExRCA successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=webmail.tgcsnet.com, OU=Domain Control Validated, O=webmail.tgcsnet.com, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name webmail.tgcsnet.com was found in the Certificate Subject Common name.
    Validating certificate trust for Windows Mobile devices.
    The certificate is trusted and all certificates are present in the chain.
    Test Steps
    ExRCA is attempting to build certificate chains for certificate CN=webmail.tgcsnet.com, OU=Domain Control Validated, O=webmail.tgcsnet.com.
    One or more certificate chains were constructed successfully.
    Additional Details
    A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
    Analyzing the certificate chains for compatability problems with Windows Phone devices.
    Potential compatibility problems were identified with some versions of Windows Phone.
     Tell me more about this issue and how to resolve it
    Additional Details
    The certificate is only trusted on Windows Mobile 5.0 with the Messaging and Security Feature Pack and later versions. Windows Mobile 5.0 devices won't be able to sync. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network
    ExRCA is analyzing intermediate certificates that were sent down by the remote server.
    All intermediate certificates are present and valid.
    Additional Details
    All intermediate certificates were present and valid.
    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 = 9/26/2010 12:39:45 AM, NotAfter = 9/18/2015 2:10:28 AM
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
    Additional Details
    Accept/Require Client Certificates isn't configured.
    Testing HTTP Authentication Methods for URL https://webmail.tgcsnet.com/microsoft-server-activesync.
    The HTTP authentication methods are correct.
    Additional Details
    ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic
    An ActiveSync session is being attempted with the server.
    Testing of an Exchange ActiveSync session completed successfully.
    Test Steps
    Attempting to send the OPTIONS command to the server.
    The OPTIONS response was successfully received and is valid.
    Additional Details
    Headers received: MS-Server-ActiveSync: 8.3
    MS-ASProtocolVersions: 1.0,2.0,2.1,2.5,12.0,12.1
    MS-ASProtocolCommands: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,ValidateCert
    Public: OPTIONS,POST
    Allow: OPTIONS,POST
    Content-Length: 0
    Cache-Control: private
    Date: Mon, 17 Oct 2011 12:15:04 GMT
    Server: Microsoft-IIS/6.0
    X-AspNet-Version: 2.0.50727
    X-Powered-By: ASP.NET
    Attempting the FolderSync command on the Exchange ActiveSync session.
    The FolderSync command completed successfully.
    Additional Details
    Number of folders: 214
    Attempting the initial sync to the Inbox folder. This initial sync won't return any data.
    The Sync command completed successfully.
    Additional Details
    Status: 1
    Attempting to test the GetItemEstimate command for the Inbox folder.
    ExRCA successfully received the GetItemEstimate response from the server.
    Additional Details
    Estimate: 18 messages

     

     

    Both tests were successfull

     

    but in the above one I found this warnng

    Analyzing the certificate chains for compatability problems with Windows Phone devices.
    Potential compatibility problems were identified with some versions of Windows Phone.

    any thoughts

     

    Thanks

    Tom


    Thomas R Grassi Jr
    Monday, October 17, 2011 12:26 PM
  • Got it to work

    Issue was that WIFI was turned on once I turned off the WIFI feature I was able to connect

    Also you must add the domain name it is not optional as the setup claims it is required

    Thanks for all your help

    Tom


    Thomas R Grassi Jr
    • Marked as answer by TRGOneCare Tuesday, October 18, 2011 4:14 PM
    Tuesday, October 18, 2011 4:14 PM
  • FYI sometimes the domain name needs to be in all caps.  Not sure why but I discovered this with some of my users who got new iPhones.  I realize the OP already found a solution but this is for anyone else who finds this thread in their search.
    Monday, November 21, 2011 6:31 PM
  • I had my phone setup correctly, was getting Exchange e-mail, then it stopped working.

    We had just updated some server software, maybe that was the start of it?  Who knows.

    I deleted the account and tried to set it up again - no go - could not verify account, could not connect to server.  Tried every combination of SSL on/off, Wi-Fi on/off, etc... for hours.

    What finally worked for me was to use the IP address for the Server instead of the name, and when entering my Username, I put a \ in front of the name.  Suddenly it could immediately verify, connect, and sync my Exchange e-mails and calendar. 

    When I go into Settings now and look at the Exchange settings, the Username appears WITHOUT the backslash, but it had to have the backslash there when setting it up before it would work.  Sigh.  Best of luck.

    Saturday, January 28, 2012 2:07 AM