11248 Views Previous 1 2 Next 29 Replies Latest reply: Sep 22, 2008 3:28 PM by damyale Go to original post
When I was not syncing but not getting any errors, I could not access OMA as I would get an error message that indicated it was not working (sorry, I don't remember specifically what it said). That's when I figured out the solution that I documented here:
Once I had completed this, everything worked and the iPhone synced and I started getting messages pushed as well. Your ability to log in to OMA successfully makes me think that everything is fine on the Exchange server side, but you may have an issue on the iPhone side. I'd try a couple of things to see what happens. First, it wouldn't hurt to go through the Exchange server and verify the settings that are in my other post, above. Second, I'd delete the iPhone's Exchange account and recreate it to see if that might fix it up.
Finally, if none of these things work, I would try using the domain name with your User ID in the iPhone setting as in:
DomainName\UserID which would look something like this, MyCompany\jane.doe
Also, be sure that you're using a backslash ( \ ) between the domain name and the user ID and not a regular or forward slash ( / ). If you're already using the domain name, try taking it off and only using your user ID.
It would also help to know which version of Windows Server you are running. SBS or Regular.
There's no hotline, other than AppleCare, that I know of, so we're pretty much on our own. From your error message, I'd guess that you're using the wrong domain name. The external domain name is usually different that what you would see in looking at your Outlook account settings.
One of the usual formats, though your Admins can pretty much call it anything they want to, is to add 'mail.' to the front of your external domain, i.e. if your email address is email@example.com, your email server's external domain name would be mail.mycompany.com Is that what you're using? If not give it a try.
Also, as I mentioned above, you may need to add your internal domain name to your user ID in your iPhone's account settings. You can find this by right-clicking on the My Computer icon on your desktop or in your Start menu and selecting Properties. From there, click on the Advanced tab and then click on the Settings button in the middle under User Profiles. Be patient, as it may take a few moments for the User Profiles window to come up. When it does, find your user name and the domain name will be everything to the left of the backslash in front of your user ID. If you find your username in the list twice, one of them will likely be your computer's name. You can try both in your iPhone as the wrong domain name won't hurt anything. Be sure to Cancel out of the User Profiles and System Properties windows so that you don't change any settings.
Ok, talked to IT and I got the boring "Corporate is standardized on Blackberry so we don't support other types of wireless device"
Very open minded..... grrrrrrr !
Anyway, I'll continue using SyncML and MobileMe with my Mac at home to Sync my email, contact, calendar and Global adress book.
Thx folks for the help with this Activesync thing.
we just got some iphones and plan to implement the ms active sync soon.
right now i am using VPN then configure the iphone exchange settings to one of my owa servers.
works great for mail and contacts but calendar comes out weird.
Anyway, this method seems to really drain the battery life, and I was wondering if anyone knows how the battery life will be once we get the active sync in place?
i even have 3g turned off, location services off and bluetooth off.
Message was edited by: skp_sr
First of all, thank you very much for your reply.
I followed exactly your email to find the Domain name but i get the same error.
In our company to logon to the exchange server using the webmail I use the following address : http://webmail.mycompany.com. And I use the same address for the Exchange ActiveSync Host in the iPhone configuration utility.
So if you have any other idea, I'll appreciate.
Where do you see the error message? On the iPhone?
If you go into Safari and type in your webmail address does Outlook Web Access come up and allow you to log into your email on the Exchange server?
If that does work, type in your webmail address again and add '/oma' (without the quote marks) at the end and see what happens.
If any windows smartphone or Pocket PC quickly and reliably connect to MS Exchange server 2003 SP1 or newer, why would Apple force Companies to upgrade to SP2 or higher in order to use the iPhone?
My company's IT department wants no part in upgrading the Exchange server as they are "busy" with other tasks. They will offer no help in getting my iphone to connect.
Why can't apple provide instructions or a patch to allow the use of EAS 2003 SP1 ?
This feature is one of the most touted improvements on the iphone from 1G to 3G. In a way I feel cheated as I cannot use this feature..... PRECISELY the reason why I bought the iPhone 3G !
I have submitted a support ticket for this issue, and it has gone all the way to "Apple Engineering", their reply was that they cannot help with my server settings. They claim the problem is not the iphone.
Seems to me that there is lots of folks in the same boat. Our time is running out as August 11th is last day to return the device. I urge Apple to reconsider by providing a solution to this issue, surely an oversight in Apple's plan.
why would Apple force Companies to upgrade to SP2 or higher in order to use the iPhone?
Security. Admins can remote wipe the device if it is lost or stolen. This allows the iPhone to compete in the workplace because Windows Mobile and BlackBerrys can do this too.
A service pack 2 upgrade to Exchange 2003 is not a major undertaking, so I can understand your disappointment in the IT lack of effort on that front.
I think we may be onto something here. At least for us. I have a similar setup. I'm not sure what happens on the inside.
I have a Exchange server on the inside of a firewall. It's has a name like boo.domain.local, which by the way I can access on the inside of the network.
I then have my router configured to port translate so that all traffic port 443 is forward to an internal IP.
Under this configuration, OWA works, SSL works with a cert issues with cert server and installed roots on the iphone (via iphone configuration).
It's some domain naming scheme that the iphone doesn't like. It must have something to do with that. Maybe it doesn't like port forwarding. Anyone have same issue?
I now everything working and in the environment specified. I ended up calling the guy. My basic config was good, it was just the settings in Exchange and in my iphone that were wrong. The guy was very professional and got it fixed fast. I feel kind of dumb as I should have tried some of the fixes. Give him a call. He's well worth it.
Alright, here's a tough one.
I've got several customers with W2K3SBS server's running Exchange with all capabilities regarding OWA, RPC/HTTP & OMA.
Every customer that has needed an iPhone configured for Exchange Activesync has worked like cake, not a problem until now.
I have one customer network with a few doctors that are Mac users so knowing & having experienced some of the difficulties of getting a Mac to authenticate the a Windows AD with the .local domain extension I decided (before the iPhone was to have Activesync) to contruct this W2K3SBS network with a .lan extension per advice of some tech articles & forum info from other users that experienced .local issues with how Windows AD vs. Mac integration.
On this particular network iPhones will not fully connect to Exchange Activesync the same way. The setup & verification works but no data ever changes hands between the iPhone & W2K3SBS server & no errors are identified.
These same iPhones will work fine with connection to any other W2K3SBS network & I've checked every setting, cross checked, tweaked, un-tweaked.
Anyone have any similar issue or suggestion on what the issue truely is?
I was getting this too, but was able to resolve the issue today.
WARNING: the following must be done by a network administrator with access to the domain controller and knowedge of adsiedit.
The problem has to do with the msExchOmaAdminWirelessEnable attribute on the user account. There is a news group posting at (http://groups.google.com/group/microsoft.public.windows.server.activedirectory/browsethread/thread/3da065527e85cbb1/366c87fdeb8bec72) that gives an overview of the appropriate values. My lucky number turned out to be 32.