We experienced something the like with out AOL users. It turned out to that it was caused by a bad routing entry at the firewall.
AOL uses 172.x.y.z IPs as did our customer. However, the netmask for private class B ip addressing scheme is not 255.255.255.0 and after fixing this, aol users were able to do OWA:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.