New IP and router for owa and exchange. Can't reach OWA.
I am currently running exchange 2007 with no problems form our T1. We just had Fios installed and we are getting rid of the T1 in favor of verizon. I have not transferred public DNS yet to the new ip addresses because I want to make sure there will be no down time with my new setup.
I purchased a Netgear Prosafe 338 router and hooked it directly to the verizon ONT through the ethernet connection.(the actiontec router is really bad so I bypassed it entirely). I have internet connection on a static IP with a block of 13 addresses. I added port forwarding rules 25, 80 and 443 to my internal exchange server from one of the extra 13 IPs. I can reach the Netgear 338 for remote admin outside the private network (with port 8080). I also set up a test machine with just port 80 and reach that from outside as well.(i recieve an IIS HTTP screen).
But when I try and reach the mail server to OWA nothing. I am not using a name yet "mail.server.com " beacause of the DNS not being transfer externally yet. Just IP address. 77.xxx.xxx.xxx.
Here is what is odd. Inside the private network if I type the pulbic IP adrress I can access OWA no problems. That is if I am using the Netgear as my Gateway address for internet access. If I change back to the T1 gateway and type the new address from verizon, no dice. I am stumped.
Keep in mind Exchange OWA is already set up correctly and working with my 3com FIrewall and the T1. I can use "mail.server.com" or an IP address internally and externally to access it.
I am running an ssl cert
The exchange server is still hooked up to the T1 Gateway.
I also tried every Setting with the Provided Actiontec Router with their tech support for two hours and the same results happen.
I hope I explained this as best as possible.