Link to home
Start Free TrialLog in
Avatar of tganus
tganus

asked on

Can't setup "OWA" access on a droid phone.

Hi Experts!

We have a really strange problem with a newly installed server (SBS 2011) and OWA access via droid smartphones.

Here's the deal.  I know this isn't a firewall issue, etc., because I can use OWA from anywhere using a web browser and log in as any user and it works fine.

When I try and setup the user accounts from a droid smartphone (I've tried SEVERAL different brands/models), I can't get the user accounts to setup.  Sometimes they'll setup, but not sync, other times they won't setup at all.  However, I can setup the admin account on those droid devices and they work just fine.

So, why will the admin account work fine, but the user accounts won't?

Thoughts?

Thanks!
Avatar of xterminator
xterminator
Flag of Belgium image

I have seen this happen with user logon rights set.
The 'Logon To' feature of these users were set to a single computername inside the network. OWA wasn't working, set them to 'allow to logon to any computer' and OWA started working.
As the Admin account is working, it doesn't sound like an certificate issue.
Avatar of tganus
tganus

ASKER

I checked this setting on the user in question and he already showed "Log into all computers" under his accounts Properties.
I also tried disabling the requirement for a device password in Exchange Activesync setting but this had no effect.

It's frustrating, my iphone accepts his info, server address, everything, I get the cert error, and then get the checkmarks showing all the information was accepted and verified but then I get a "Cannot get mail - The Connection to the server failed" error when refreshing the inbox.
Avatar of Craig Beck
Have you actually allowed those user accounts the right to use ActiveSync or OWA?
ASKER CERTIFIED SOLUTION
Avatar of tganus
tganus

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tganus

ASKER

Researched the problem more fully and found it wasn't an exchange error at all, but an Active Directory permissions issue.