• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 222
  • Last Modified:

Exchange, not Exchanging

Hi Experts,

Weird one... I have never seen this behavior before

Here's what we have 3 x Exchange 2010 (WNLB) CAS Array & 3 x Exchange 2010 MBX Servers in a DAG - all running on wIN 2008 R2 VMWare (ESX5)

All bar 2 servers can communicate... ping, UNC paths etc... so obviously, i have a Public Folder replication issue with these 2 servers.

CAS 3 & MBX will just not "talk" to each other

I changed IP's on the CAS' NIC (updated the WNLB etc..) - no good

I added another vNIC to the CAS server, assigned an IP etc... bingo - can ping/map drives etc...  but, alas i cannot add the new NIC to the WNLB CAS Array... Grrr!

I cam across this KB article - but applicable in our case: http://support.microsoft.com/kb/2649727

We are running Exchange 2010 SP3 UR2

Any ideas guys?


  • 3
1 Solution
Only a little question: did you use the good IP/mask for your networks?
Sometime an IP becomme unavailable because that IP is the broadcast IP if we use a specific mask.

parksvAuthor Commented:
Thanks Dan...  barring the last octet of the IP Address, all other settings across the servers are identical - same subnet - /16, same default gateway, same DNS...
parksvAuthor Commented:
Found the problem... ARP tables on both these servers had invalid MAC addressed or each other (dynamically learned) - very strange.

i created new static ARP entries & all was good.

parksvAuthor Commented:
Issue resolved as a result of static ARP entries
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now