Exchange 2007 SP1 with GoDaddy Cert - iPhone cannot verify cert

Hi Everyone,
My school has just moved to Exchange 2007 and I'm trying to connect my iPhone to it. We haven't changed any settings on the Exchange server really that relates to ActiveSync (at least as far as I can tell). We're using a GoDaddy wilcard SSL cert with the site for OWA and (I hope) ActiveSync.
From what I can see, Apple has included all of the GoDaddy Intermediate and Root certs in OS 3. I have manually installed these certs again on my iPhone (the one I'm testing with) by emailing them to myself. This hasn't helped with the issue...
When trying to add the Exchange account on the iPhone I'm getting an "Unable to Verify Certificate" error. The error makes no mention of autodiscovery (which it should be using), so I'm not sure if it has anything to do with that. I'm really not sure what to do at this point since we're all new to Exchange, and I only have used my iPhone through Exchange with Google in the past.
Thanks,
-MRCUR

Ever hear anything back on this? I too have an iPhone (3G) and would like to connect it to a GoDaddy Exchange server. No luck so far.

Similar Messages

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Upgrade Exchange 2007 sp1 to sp3

Good day,
I have 3 exchange 2007 sp1 servers in my domain in different subnets. I need to upgrade all of them to sp3. i started with one branch server that is not in the same site with the domain schema master and im getting errors during instalation preparations
that - "    Organization Checks              ......................... FAILED
     Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory site as the schema master (Default-First-Si
te-Name).
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Hub Transport Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Client Access Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Mailbox Role Checks              ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
My question is do i need to first upgrade the one in the same site with the scema master? and what will happen to the other remote server in different subnets?? how will i upgrade them given these errors?
Regards,
Brian

Good day,
I have 3 exchange 2007 sp1 servers in my domain in different subnets. I need to upgrade all of them to sp3. i started with one branch server that is not in the same site with the domain schema master and im getting errors during instalation preparations
that - "    Organization Checks              ......................... FAILED
     Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory site as the schema master (Default-First-Si
te-Name).
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Hub Transport Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Client Access Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Mailbox Role Checks              ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
My question is do i need to first upgrade the one in the same site with the scema master? and what will happen to the other remote server in different subnets?? how will i upgrade them given these errors?
Regards,
Brian
Prepare the domains as required. You have to prep the forest first for SP3 before upgrading Exchange itself
Follow all the instructions
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
Prepare Active Directory and Domains
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Improper decoding of base64 encoded attachment on Exchange 2007 SP1

I'm using Exchange 2007 SP1. My java application sends email to users of exchange 2007 SP1. The email contains an email as an attachment which is base64 encoded . This email when sent to users on exchange 2007 SP1 shows blank attachment. The same email when sent to users on different exchange (e.g. Exchange 2003) shows the correct attachment i.e. the attachments are not blank. While sending the mail i'm setting name of the attachment in Content-Type header but it is not there when we look at the rfc contents of the mail received on ex 2007 SP1. It seems exchange 2007 is not able to decode the base 64 contents properly. Below are the rfc contents of the mail which show few headers in the attachment part instead of the base64 content. Please suggest some solution to it. It's urgent.
Received: from test80.psjpr.com (192.168.0.243) by exchange01.psjpr.com
(192.168.0.138) with Microsoft SMTP Server id 8.1.263.0; Fri, 11 Apr 2008
18:53:12 +0530
From: Admin <[email protected]>
To: test test1 <[email protected]>
Date: Fri, 11 Apr 2008 18:53:12 +0530
Subject: Retrieved from : testingggggg
Thread-Topic: Retrieved from : testingggggg
Thread-Index: Acib1zFeboxSL6S4RuaeI0AaCou0pQ==
Message-ID: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: exchange01.psjpr.com
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Content-Type: multipart/mixed;
boundary="_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_"
MIME-Version: 1.0
--_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The message you requested is attached.
--_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_
Content-Type: message/rfc822
Subject:
Thread-Index: Acib1zFexS+KMQAOSD+lcMut076Wyg==
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
--_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_--

Did you ever this to work ?

BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

Hello,
I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
the migration to Exchange 2010?
Thanks,
HA

Hello Ha20,
Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migrating Exchange 2007 SP1 to Exchange 2013

Follow the Exchange Deployment Assistant to the letter and you will not have issues.http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspxAnd my guide:You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option...

This is a slightly daunting task I must admit. I am migrating an old exchange 2007 SP1 installation over to 2013 SP1 and looking for good advice and/or tips. I am finding the whole thing slightly unnerving as there seems to be about a million caveats give or take a few thousand. There seems to be about the same amount of tips, tricks and guides as well, but sadly they are not quite consistent and some are down right contradicting each other.I'm reading similar questions here on spiceworks, and it seems like I'm reading about one horrible episode after another. By now, I assume most have migrated already, so I though I might pick some brains and figure out the best way to do this ;)Might software like CodeTwo Exchange Migration or Dell Migration Manager be a good idea? Are there maybe similar tools available as well?Any feedback is very...
This topic first appeared in the Spiceworks Community

Exchange 2007 EXCDO 8206 error in Exchange 2007 SP2 with Rollup 4

Dear sir,
    We have a problem on Exchange 2007 Server. When user use OWA to access web mail calendar, server event log will show EXCDO error 8206:
Calendaring agent failed with error code 0x8000ffff while saving appointment
Type: Error
Event ID: 8207
Category: General.
     Moreover server becomes working in very slow web mail response during any user click web mail calendar.   Server performance return back after error message appeared in event log.
It doesn't has problem if using Outlook to access mailbox calendar.
Any suggestion to fix it ?
Joe

Hi Joe,
We are also finding the same issue with getting that EXCDO error. The problem stemmed when users noticed some previously accepted appointments disappeared (As I suspect you discovered with your users).
The workaround has been to get the user to accept the appointment again by going into deleted items, this seems to add the appointment as it should have the first time.
We have done the following but it didn't fix the problem:
Disabled extra SEP features on the clients - No Change
Disabled non-essential Outlook add-ons - No Change
Removed BES Express and CDO MAPI From Exchange server - No Change
Disabled MS Defender on Exchange - No Change
Fixed any Public folder errors - No Change
Disable Window services WSS and UNC sharing feature in Active Sync - No Change
Also ensured Autoupdate and auto process was enabled for affected users - No Change
I'm going to try the reg change mentioned in this thread but other than the built in MS Defender we don't have anti-virus on our mail server.
At first we thought it was Active Sync as it only seem to impact those with a A/S device, but now it's intermittent for other users using Outlook.  We are currently using Exchange 2007 SP3 with RU13. We are looking at trying an update
to RU14 but I am doubtful it will fix the problem. Did you have any luck finding a solution?
Thank you in Advance.

Exchange 2007 Environment with BlackBerry Enterprise Server 5

Hi,
I am planning to migrate Exchange 2007 to 2013 DAG with BlackBerry Enterprise Server 5. For BlackBerry Users, How can I configure to work with Exchange 2013? Because Exchange 2007 works with MAPI for BES but 2013 with RPC/HTTPS.
Do I need to set up new BlackBerry Server? Please advise
Regards,
Zaw Tun Naing
ZAW

Have a look in the Blackberry
KB33413.
As stated in this blog this seems to be an "all or nothing for BB mailboxes". So if you plan to migrate slowly it would be the best to install
another BB Server.

Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

HI, i need help here
I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
flow went back to normal. We then remove the program from the control panel.
Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
Much Appreciated

Symantec's support group should be able to tell you what happened.
--- Rich Matheisen MCSE&I, Exchange MVP

Exchange 2007 - Outlook Anywhere problems after installing new SSL cert

*** Original thread posted on wrong forum ***
Hi all,
Exchange 2007 environment (2x CAS, ISA2006). Not much familiar with Exchange.
Problem: 20-odd machines off the domain use Outlook Anywhere (XP with Outlook 2010). AUthentication pop-up and not able to connect.
Company has recently changed its name and we have to renewed the SSL cert. Previous SSL cert. was issued to: webmail.oldcompname.co.uk (several SANs on that cert., including internal server names).
Applied for a new UCC SSL cert issued to: newcompanyname.com (also includes webmail.newcompanyname.com ; autodiscover.newcompanyname.com + old SANs).
The setting on those machines point the proxy to the following:
Https://webmail.oldcompname.co.uk (which is fine since it is in the cert and can be accessed)
Only connect to proxy servers that have this principal name in their cert.:
msstd:webmail.oldcompname.co.uk (I believe this is the problem since the new UCC SSL cert. was issued to newcompanyname.com).
Browsing technet + internet it seems that I need to look into OutlookProvider EXPR.
When I run Get-OutlookProvider everything is blank (I believe I should be concerned to EXPR only for Outlook Anywhere).
I am thinking of running: Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:newcomanyname.com
My only concern is whether this might break something else in the Exchange environment, especially as we have 100+ users on smartphones connecting via SSL on webmail.oldcompname.co.uk
Is it save to run this command? Do I need to re-start IIS? Do I need to look into any settings on ISA2006?
Comments/help are much appreciated.
Regards

Hi,
According to the description, I found that we re-new a SSL certificate.
"I am thinking of running: Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:newcomanyname.com"
Just do it. Then remove the old certificate on ISA server and install a new one.
Found a similar thread for your reference:
Renewal of SSL certificate in exchange 2007 with ISA 2006
http://social.technet.microsoft.com/Forums/exchange/en-US/25770038-8491-470a-92fa-8ae50674b7a6/renewal-of-ssl-certificate-in-exchange-2007-with-isa-2006
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

OWA functionality in Exchange 2007 coexistance with 2013

I have conexistance environment with Exchange 2007 and Exchange 2013. Out of about 1200 users we have 25 test users in the 2013 environment. The problem we are seeing is when a 2013 mailbox has "Full Access" to a 2007 mailbox and tries to connect
to that mailbox through OWA 2013 the connection always fail. I can attach the mailbox in Outlook with no problems but cannot open that mailbox through OWA 2013. Any thought?

See if this helps. It's not an exact match for your versions, but I think it's what you need to look at.
http://support.microsoft.com/kb/981541
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes

Hey all,
So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
AD, etc. But I'm wondering if someone can break it down for me.
http://1drv.ms/1lWjLqG
The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
Original Design
The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
Migration/Hybrid Design
Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
Migration from Exchange 2007 to Exchange 2013
I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
The latest Service Packs and CUs are installed in both.
What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
SpecialBank that users are actively using.
I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
if I need to in order to make the migration transparent to users.
Can anyone help?

Hi ,
From you description i came to know contoso is the resource forest and special bank is the account forest .
You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
Regards
S.Nithyanandham
Thanks S.Nithyanandham

How to view Exchange 2007 Public folders, calender on iphone

How to view Exchange 2007 public folders mainly the calenders on the iphone?

Not possible.
Sent from my iPad.

Upgraded to Exchange 2007 - Problems with opening attachments in e-mail Treo700wx

We upgraded our server at work to Exchange 2007. Ever since then, there have been multiple problems, on of which I am not able to open pdf files, excel or word files on my handheld 700wx. Anyone else have this problem. Talked with Verizon, they suggested downloading a new version of the pdf viewer. That didn't work. Looking for any suggestions.
Post relates to: Treo 700w (Verizon)

Hello!
Since your company is now using 2007, good chance you will need a Windows Mobile 6 and up phone. Please install this update to get your phone to windows mobile 6.0:
http://kb.palm.com/wps/portal/kb/common/article/10133_en.html
Be sure to follow the instructions on the page.

Autodiscovery from external Exchange 2007 SP1

Dear all,
We have 1 Exchange 2007 and 1 CAS server running and a Terminal Server. All Outlook 2007 clients are connecting using HTTPS/RPC internally and external. Now our problem is that when we try to configure an outlook client 2007 from the outside, that the "Online Search for your server settings" fails. We constantly get the credentials (u/p) prompt which is provided the correct credentials but are not accepted.
From inside (for example on the Terminal Server) everything works fine (incl. OAB, OOF, etc). So this should be something with login to autodiscover.
Conclusion:
When we try to connect to: https://externaladdress.domain.net/autodiscover/autodiscover.xml (from the CAS server) we can logon with every valid credential. Now when we try to connect to the above mentioned address from ANY other internal server, or external address, we are not able to login and are constantly prompted with the UserName and Password window.
Does anybody have a clue what's wrong here?
Regards,
David.

Hi Scott and Rajnish,
Thanks for your response.
We do not use a firewall to be honest (at this moment). I forgot to mention that we also use a url autodiscover.domain.net as a redirect to webmail.domain.net (our CAS server). Redirect seems to work fine, as I tried to connect to: autodiscover.domain.net/autodiscover/autodiscover.xml and I'm prompted with username and password window (which also does not authenticate). The
The report from the url: https://www.testexchangeconnectivity.com/
Testing RPC/HTTP connectivity
RPC/HTTP test failed
Test Steps
Attempting to test Autodiscover for EMAIL REMOVED
Testing Autodiscover failed
Test Steps
Attempting each method of contacting the AutoDiscover Service
Failed to contact the AutoDiscover service successfully by any method
Test Steps
Attempting to test potential AutoDiscover URL https://domain.net/AutoDiscover/AutoDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps
Attempting to test potential AutoDiscover URL https://autodiscover.domain.net/AutoDiscover/AutoDiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps
Attempting to contact the AutoDiscover service using the HTTP redirect method.
Failed to contact AutoDiscover using the HTTP Redirect method
Test Steps
Attempting to resolve the host name autodiscover.domain.net in DNS.
Host successfully resolved
Additional Details
Testing TCP Port 80 on host autodiscover.domain.net to ensure it is listening and open.
The port was opened successfully.
Checking Host autodiscover.domain.net for an HTTP redirect to AutoDiscover
Received Redirect (HTTP 301/302) Response successfully.
Additional Details
Attempting to test potential AutoDiscover URL https://webmail.otherdomain.net/Autodiscover/Autodiscover.xml
Failed testing this potential AutoDiscover URL
Test Steps
Attempting to resolve the host name webmail.otherdomain.net in DNS.
Host successfully resolved
Additional Details
Testing TCP Port 443 on host webmail.otherdomain.net to ensure it is listening and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The certificate passed all validation requirements.
Test Steps
Attempting to send AutoDiscover POST request to potential autodiscover URLs.
Failed to obtain AutoDiscover settings when sending AutoDiscover POST request.
Test Steps
Attempting to Retrieve XML AutoDiscover Response from url https://webmail.otherdomain.net/Autodiscover/Autodiscover.xml for user EMAIL REMOVED
Failed to obtain AutoDiscover XML response.
Additional Details
A Web Exception occurred because an HTTP 401 - Unauthorized response was received from Unknown
Further I've spend more than 1 week to find a solution, and read a lot of articles, including the one Scott mentioned in his post.
I hope that we can resolve this :-(
Regards,
David.

Exchange 2007 SP1 with GoDaddy Cert - iPhone cannot verify cert

Similar Messages

Maybe you are looking for