Active Sync Issues with Iphone 4 and exchange 2003

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Done all of that, and then did the tutorial links below that.
The exhange VD .net version is 2.0.50727 - no drop down allowed to change it to 1.x.x.x - The active-sync VD DID allow me to change down to 1.x.x.x.

ASKER

Another thing to mention is when choosing authentication I enter domainname, if I click the select button to see whats available it has domainname.local but I do not use that.
After resetting all IIS settings and having it all be re-created the default name that shows up (ONLY under the active sync VD) is olddomainname.
I did a domain rename about 3 months ago and find it odd that the olddomain keeps popping up once in a while, its also interesting that when I setup an outlook profile and type exchange server name and type the FQDN server.domainname.local, and click "Check" it underlines the servername but changes it to server.olddomainname.local - VERY strange as I cant even ping olddomainname.local or anything, but outlook works fine and has no issues!

how did you rename your domain ? using rendom ?

ASKER

@Sunnyc, I will check version of iphones. In my original post I mentioned using the testexchange website and posted the results that I get (500 error)

I need the verbose results with SSL checked.
Can you post that please.

ASKER

User says its on 4.0 and "up to date"...

ASKER

Here are results (what do you mean SSL checked?, ignore SSL? I did not ignore because its a 3rd party godaddy cert).

An ActiveSync session is being attempted with the server.
     Errors were encountered while testing the ActiveSync session

      Test Steps

      ExRCA is attempting to send the OPTIONS command to the server.
     OPTIONS response was successfully received and is valid

      Additional Details
     Headers received: Pragma: no-cache
Public: OPTIONS, POST
Allow: OPTIONS, POST
MS-Server-ActiveSync: 6.5.7638.1
MS-ASProtocolVersions: 1.0,2.0,2.1,2.5
MS-ASProtocolCommands: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,ResolveRecipients,ValidateCert,Provision,Search,Notify,Ping
Content-Length: 0
Date: Fri, 03 Sep 2010 13:46:50 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET

      ExRCA is attempting the FolderSync command on the Exchange ActiveSync session.
     The test of the FolderSync command failed.
      Tell me more about this issue and how to resolve it

      Additional Details
     Exchange ActiveSync returned an HTTP 500 response.

it should be 4.0.2

4.0 has an issue with SYNC to Exchange
Apple released a fix
i will post back.

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

The fix for the Apple iOS4 with Exchange is linked to in my blog for this problem:
http://alanhardisty.wordpress.com/2010/07/02/apple-ios4-issues-with-iphone-4-3gs-3g-and-exchange/

Alan - aha...
rhwimmers - there you have it > Alan's article.
That's the bible around here @ EE for troubleshooting iPhone issues.

4.0.2 is stable, I havent heard issues from that - if you can, please upgrade to 4.0.2

ASKER

Have been going through that article or doing those things on and off for a week now. hoping this iphone OS fix is it, although the testexchange things comes back bad and I wouldn't think that it would since its not running apple OS?

If you have been through my article, KB883380 and then the additional fix for Error 500 and still no joy - then Microsoft is the next port of call I'm afraid.

although the testexchange things comes back bad and I wouldn't think that it would since its not running apple OS?
>> ExRCA (TestExConn) tests against the Microsoft Exchange Activesync - it doesnt test against the iphone OS.
It's a simulator to check if everything is working ok over there.

ASKER

Still not having much luck - however...I DID notice that when I reset IIS (for the 5th time by now) that the virtual directory for active-sync authentication default is olddomainname - if I click the browse I see newdomain.local, but I have just been typing in newdomain (no .local) per the instructions ive seen several places... This is bothsome and I feel it might have something to do with the issues... I found this article
http://www.freelists.org/post/exchangelist/Exchange-2k3-Post-Domain-Rename
Which unfortunatley has NO responses because it is almost identicle to what im running into - I went to turn forms based authentication back on just as a hunch and then I got that same error... I ran the netdiag and i DO see the old domain name

Registered Service Principal Names:
XOsoftEngine/sbexch01.newname.local:25000
exchangeRFR/sbexch01.oldname.local
exchangeMDB/sbexch01.oldname.local
HOST/sbexch01.newname.local
SMTPSVC/sbexch01.newname.local
exchangeRFR/sbexch01.newname.local
exchangeMDB/sbexch01.newname.local

I would feel better if I didnt see the oldname anywhere, but cant seem to figure out how to remove it?

Have you followed kb883380 method 2? That might resolve the issue.
http://support.microsoft.com/kb/883380

ASKER

Yeah, ive actually tried all 3 methods at different times....

ExRCA is attempting the FolderSync command on the Exchange ActiveSync session.
The test of the FolderSync command failed.
Tell me more about this issue and how to resolve it

>> did you click on the tell me more link

ASKER

Yes, it leads to the same links as everyone here has posted....
http://technet.microsoft.com/en-us/library/dd439375%28EXCHG.80%29.aspx

Here is the closing comment from another question I worked on - it may be worth checking:
"So after talking to our good friends at Microsoft here's the solution:
As it turns out the in ability to authentication was do to.....
The exchange's servers virtual directory for the mailboxes was visible.
Which in turn throw an error preventing the authentication.
Here is the Registry entry: HKEY_LOCAL_MACHINE --> CurrentControlSet --> Services --> EXIFS --> Parameters --> DriveLetter=M
I removed "M" so now it empty or blank and BadaBing BadaBoom "Smart Phones" now sync. "
Failing that - Microsoft is the next port of call.

ASKER

Well, Microsoft fixed the issue. It DID have to do with my domain rename as I suspected - we did 2 things that seemed to fix things....
1. Deleting the exchangeRFR/sbexch01.oldname.local from the registered SPN using setspn -d etc (neither of us knew if this actually did help, as it still lists the oldname in the setspn -L)

2. I am 99% sure THIS is what actually fixed it... Going into adsiedit utility then gong to configuration, configuration, services, exchange, first organization, administrative groups, servers, servername, rightclick and go to properties on the servername, then under attributes go down to network address... It had ncacn_ip_tcp:servername.oldname.local - click remove, change to ncacn_ip_tcp:servername.newname.local
- I guess something that didnt get changed during the domain name change project for whatever reason.
Whew, that was a tough one - 1st time ive ever had to call MS in over 10 years!

ASKER

Thanks for the effort on this one - Alan, maybe add this to the guide in the small chance someone does a domain rename and has same issue?