We found a fix for all you iPhone/iPad users. It's a known issue with Apple devices, apparently.

The work-around is here.

Thank you Princeton IT Group for the help!