SBS 2003 R2 - Outlook Mobile Access issue - "your account is not configured for wireless access"

I have a SBS 2003 R2 machine and am in the process of configuring OMA. I've rerun the CEICW to enable OMA and mobile access is enabled in user properties.

When I try to log in, either on the LAN using http://servername/oma or using my mobile with http://dnsname/oma, I get the error message:-

"Your account is not configured for wireless access"  

...which on checking Google has something to do with smtp addresses, but I'm a bit lost at this point.....any help much appreciated.

CSHTechAsked:
Who is Participating?
 
CSHTechConnect With a Mentor Author Commented:
Have resolved the problem. The exchange-oma file path under Default Website was pointing to a previous email address. Once I added an email address with that domain name into User Properties, the server found the correct mailbox.
0
 
CSHTechAuthor Commented:
Further info -

I have a dynamic IP address and am using the DynDNS Updater to point to a DynDNS name, so my accessing via mobile are using that address.
0
 
suppsawsCommented:
Hello CSHTech,

I guess you want to setup push email instaed of OMA?
http://sbs.editme.com/outlook

Regards,

suppsaws
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
CSHTechAuthor Commented:
suppsaws

I'm not really looking for 'push' technology as such, as I already have that on my Blackberry from my ISP. I'm after more of a facility to passively check my emails whilst I'm out of the office as I'm finding that my server is scooping up some emails from my ISP before they are pushed to my Blackberry.

I'd rather not go down the Blackberry Enterprise route as I want to keep cost to a minimum, so OMA is ideal.
0
 
suppsawsConnect With a Mentor Commented:
it's https://FQDN/oma
make sure the cert is pointing to the correct FQDN
0
 
CSHTechAuthor Commented:
Have tried http and https on both internal and external addresses - same problem.

As mentioned in original post, it may be something to do with smtp addresses but that's as far s I understand it.......
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.