Link to home
Start Free TrialLog in
Avatar of jgutierr76
jgutierr76

asked on

Trying to setup Active sync on Exchange 2013 to coexist with 2007

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!
Avatar of jrlingam
jrlingam
Flag of India image

In order to confirm that firewall is not causing the issue, the best option is to remove the firewall and point the public network to directly hit the CAS servers. This will work in most cases.

Microsoft support will not accept to provide any further support until you by pass the firewall and directly route the traffic to CAS servers and still face the issue.

Also provide your wireshark traces to the firewall / network teams and ask them to check if any blocking is happening. They will be able to better analyse the network traces.
ASKER CERTIFIED SOLUTION
Avatar of Steve
Steve
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial