I have a 2-node Exchange 2003/SP2 NLB front-end cluster (with no port restrictions). OWA requests are processed by both nodes but Activesync requests are only processed by one node. Activesync requests for the public IP address are translated at the firewall to the internal NLB IP address. Even if the working node is taken out of the cluster, the remaining node still does not process any Activesync requests. Internally, I can access http://(bad_NLB_node)/oma and access my Inbox via the mobile style interface. Any ideas?Kerry Moyer

On Tue, 5 Oct 2010 19:59:24 +0000, kmoyer3 wrote: >I have a 2-node Exchange 2003/SP2 NLB front-end cluster (with no port restrictions). OWA requests are processed by both nodes but Activesync requests are only processed by one node. Activesync requests for the public IP address are translated at the firewall to the internal NLB IP address. Even if the working node is taken out of the cluster, the remaining node still does not process any Activesync requests. Internally, I can access http://(bad_NLB_node)/oma and access my Inbox via the mobile style interface. Any ideas? Sounds like a topic for one of the Windows Server forums. If NLB is working for OWA it should work in the same way for everything if you haven't limited the ports. And even if you did limit the ports AcriveSync uses port 443 the same as OWA does. OMA doesn't use port 443, it uses port 80 (if I remember correctly). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP