Answered by:
Cannot ping DAG IP

Question
-
I have a two node Exchange 2010 DAG.
One is active and sits in Site A and one is passive for replication purposes and sits in Site B.
In Failover Cluster Manager, the DAG is set up with two IP addresses - one is online and one is offline.
Today I noticed that for some strange reason, the passive server at Site B cannot ping the current online DAG address at all. But it can ping other physical hosts using the same subnet as the DAG address. In fact nothing at Site B can ping the DAG address. But they can ping everything else. Everything at Site A is working perfectly. There is nothing wrong with the routing, everything checks out. Nothing is being blocked.
Why is this happening?
- Edited by khunkao Monday, March 16, 2015 6:48 PM
Monday, March 16, 2015 6:46 PM
Answers
-
Then something has to be wrong on the network configuration. Treat this as standard network troubleshooting and triple check everything.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Facebook:
XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
- Marked as answer by Winnie LiangMicrosoft contingent staff Tuesday, March 24, 2015 1:39 AM
Monday, March 16, 2015 10:16 PM
All replies
-
Is this OS Windows 2008 R2? If so look at the firewall fix that is in this post:
http://blogs.technet.com/b/rmilne/archive/2013/11/20/exchange-2010-tweaks.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Facebook:
XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Monday, March 16, 2015 7:24 PM -
It is Windows 2008 R2
I just checked and it still says "Domain Network"
Also Windows Firewall is not turned on at all.
Monday, March 16, 2015 7:45 PM -
Then something has to be wrong on the network configuration. Treat this as standard network troubleshooting and triple check everything.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Facebook:
XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
- Marked as answer by Winnie LiangMicrosoft contingent staff Tuesday, March 24, 2015 1:39 AM
Monday, March 16, 2015 10:16 PM -
Hi,
check the FW and also tracert will help you
Regards
Muthu
Thanks Muthu
Tuesday, March 17, 2015 2:29 PM