Hi all,

This morning i found an issue in my exchange 2013 server (mailbox server) which is somehow i can't ping it. It happened on 8:08 AM, so i took restart server action immediately. After the restart action, everything went smooth as if nothing happened, but in the next morning it occurs again (so far it is already occurred 3 days in a row at the same time (8th, 9th, and 10th June in the morning))

When i look at the event viewer, i found many error about failover clustering (code 1129) right before 8:08 AM.

https://social.technet.microsoft.com/Forums/getfile/667930

My questions are :

1. Are failover clustering errors (1129) which causes this exchange mailbox server can not accessible ?, if they aren't the cause for this issue, so what is actually happen to this server ?. I've check the network and it is fine.

2. Is there any way to solve this issue ?, so far what i'm doing is >>> on TCP global parameter, i disabled the receive-side scaling state by this command on cmd : netsh interface tcp set global rss=disabled

I'm looking forward to your help, thank's :)

Update 11th June 2015 : this morning the issue occured again

• Edited by M. Reza Hendrawan Thursday, June 11, 2015 2:08 AM

is this what you mean ?

"Cluster network 'Cluster Network 1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges."

yap, they're on the same subnet

Use the little "Copy" button in the event log detail.  Paste it here.

That message tells you that the Cluster Service thinks something is wrong with your network connectivity between the nodes.  Perhaps you have a bad or misconfigured NIC or switch.