In order to leave our current Exchange 2007 setup intact we have create a new namespace
email.XXXXX.com All VD for owa and active sync are pointing to it in new 2013 setup
Email.XXXXXX.com resolves to a public number that hits our Firewall and the Firewall passes traffic to internal internal network. I have verified with Firewall tech support via packet capture that the 443 traffic hits the firewall on the public side and it passes it off to private side.
Running Wireshark on both production NIC and NLB NIC on one of the cas servers the traffic never gets there. I cannot explain what is going on. Microsoft support is blaming firewall but I now have packet caps that prove the traffic is being sent from firewall to private side it just never gets there according to wireshark. The new name space is ping-able by name and number internally. I am kind of at my wits end here as to is happening..........PLEASE HELP!