DNS fix for iPhone iOS4 error in Exchange inbox

Brian Povlsen reports an Exchange problem with the new iOS4 for iPhone that produces an error in an Exchange inbox. The solution (for network administrators) is to use A records instead of CNAMEs in the DNS server:

Some individuals from the Apple Discussions forum said that they are getting the error “Server is unavailable” in their inbox on a Microsoft Exchange 2003 account. These accounts worked normally before the upgrade. Archilies has the solution: “I had the same issue. It appears that the mail client in iOS 4 does not like CNAMEs. I had to change our DNS zone to use A records instead of CNAMEs for our mail server.” This is verified by other posters on the thread.” The post about this can be found here.

E-mails deleted on Wndows Mobile 6.1 do not delete on Exchange server

This post explains how to resolve the problem that can occur on Windows Mobile 6.1 with ActiveSync synchronising an Exchange mailbox.  Thanks to Greg Johnson for a short quickfire method of resolving this.

1. Go to active sync
2. Select “Menu”
3. Select “Options”
4. Uncheck E-mail

You will get a warning about this deleting all email for this account on your Q. That’s fine, it won’t touch the email on the server. After this completes select “Done.” Then go back to Active Sync and repeat the steps above excep check E-mail this time. You’ll be back in business without having to delete and re-create the whole exchange profile.

Windows Server 2003 Event ID 3015 and 3024

After performing some routine maitenance on several server I began to recieve the above event ID in my Windows server logs.

Event Type:    Error
Event Source:    Server ActiveSync
Event Category:    None
Event ID:    3015
Date:        27/02/2009
Time:        10:09:30
User:        N/A
Computer:    xxxxxx
Description:
IP-based AUTD failed to initialize because the processing of notifications could not be setup.  Error code [0x80004005].  Verify that no other applications are currently bound to UDP port [2883], or try specifying a different port number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Server ActiveSync
Event Category: None
Event ID: 3024
Date: 27/02/2009
Time: 10:09:33
User: N/A
Computer: xxxxxx
Description:
IP-based AUTD failed to initialize. Error code: [0x80004005].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

After searching around, lots, I found that the port was being taken over by and used by the DNS server service. Unfortunately the assignment is rather random and may or may not taken control of port 2883 at anytime or any reboot.

As a workaround, you can modify a registry key to reserve the UDP port and prevent it being bound to other applications:

Windows Server 2003 or Windows XP Professional

1. Start Registry Editor (Regedit.exe).
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, point to New, and then click Multi-string Value.
4. Right-click the new value, click Rename, type ReservedPorts, and then press ENTER.
5. Double-click the ReservedPorts value, type the range of ports that you want to reserve, and then click OK.

Note You must type the range of ports in the following format:
xxxx-yyyy
To specify a single port, use the same value for x and y. For example, to specify port 4000, type 4000-4000.

Warning If you specify the continuous ports separately and if one port is reserved and not used, the next port is not correctly reserved, and it is used.
6. Click OK.
7. Quit Registry Editor.

Note You must restart the computer after you make these changes for the changes to take effect.

Steps taken from Microsoft KB 812873