Hi All,I am facing a different problem in Exchange 2007 SP1 Update Rollup 9 / Windows 2003 R2 setup, I am having a 2 node NLB of HUB/CAS servers behind a Network Firewall by Fortigate. Mailbox is an SCC cluster.There is not issue in accessing the OWA from within the Local Network, but some of the users are facing the problem in accessing OWA from remote locations connected by Internet, they simply got 'Page cannot be found', but if we check the firewall logs we are getting hits from that IP on the firewall and same has also been forwarded to the Exchange Server. We changed the IP natting from firewall to Exchange NLB Virtual IP and set it with the physical IP of the one of the HUB/CAS node and it started working fine again we cross checked by doing it vice-versa and the result was same , that is was working only after changing the IP Natting to physical machine IP.Unable to get any conclusion about where the problem exactly lies, either at Exchange Server end or at Firewall end. Because we are not facing any issue in internal network. I am also not getting any error at HUB/CAS servers.Kindly help in this to sort it.RegardsSupreet Singh

I don't have an answer as to why it isn't working in your case. In general, I prefer to publish OWA using IIS or TMG and using that server's built in server farm feature, which is more effective for Internet source traffic than NLB.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Supreet20in" wrote in message news:b45a3007-f8e1-4f85-a69a-5b3656628a55...Hi All,I am facing a different problem in Exchange 2007 SP1 Update Rollup 9 / Windows 2003 R2 setup, I am having a 2 node NLB of HUB/CAS servers behind a Network Firewall by Fortigate. Mailbox is an SCC cluster.There is not issue in accessing the OWA from within the Local Network, but some of the users are facing the problem in accessing OWA from remote locations connected by Internet, they simply got 'Page cannot be found', but if we check the firewall logs we are getting hits from that IP on the firewall and same has also been forwarded to the Exchange Server. We changed the IP natting from firewall to Exchange NLB Virtual IP and set it with the physical IP of the one of the HUB/CAS node and it started working fine again we cross checked by doing it vice-versa and the result was same , that is was working only after changing the IP Natting to physical machine IP.Unable to get any conclusion about where the problem exactly lies, either at Exchange Server end or at Firewall end. Because we are not facing any issue in internal network. I am also not getting any error at HUB/CAS servers.Kindly help in this to sort it.RegardsSupreet Singh Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."