SBS2k3 and OMA
A couple of weeks ago, my OMA stopped working on my Sprint Phone. It's a WAP enabled device, not yet up to investing in a Windows Mobile PC (drool)...
Anyway, I tried a bunch of stuff, but was really too busy to sink my teeth into it, so i gave up. The only time i used it was when i was waiting in traffic or at a client's so it was not that big of deal. Well, today i had had enough, and decided to check into it... After much consternation and even a post to my local user group, I went looking on the Microsoft site
in MSN search:
OMA Error 1805 site:microsoft.com
I was getting the 1805 in the event viewer application log on the SBS machine. Sure enough there was some info there...primarily this: http://support.microsoft.com/?id=817379 without following their instructions, screw that recreate the virtual directory, etc...I decided to check the settings on the virtual directory, in this case exchange-oma, seems to be important enough for them to point that vdir out in the tech article. So I am walking through the permissions in my existing vdir...see method 2 steps 13 and 14:
| 13. |
Under IP address and domain name restrictions, click Edit. |
| 14. |
Click Denied access, click Add, click Single computer, type the IP address of the server that you are configuring, and then click OK. |
As it turns out, my server has 3 IP Addresses
127.0.0.1
xxx.xxx.xxx.2
xxx.xxx.xxx.3
but low and behold, xxx.xxx.xxx.2 is not there! WHAT THE F!!!!!! I add it back and into the list, and sure enough test it out. WOW WILL YOU LOOK AT THAT, suddenly it works like a champ.
I love it! (again)