Network cards in Windows can be connected to one of these type of networks:īy default, the public network location type is assigned to any new networks when they are first connected.Ī public network is considered to be shared with the world, with no protection between the local computer and any other computer. If it doesn’t have a gateway configured, or if it can’t successfully ping it, it will not be able to identify the network it’s connected to and will assume it’s a public one. Windows uses gateways to identify networks.
The issue turned out to be caused by the 2 NICs we have for iSCSI traffic which did not have a gateway configured. The OS install and networking part was already configured by a someone else and it was a pretty straightforward installation. This may prevent some network communication between cluster nodes. The ‘Failover Clusters’ rule group is not enabled in firewall profile ‘Public’. In particular, the ‘Public’ firewall profile is enabled on adapter ‘ – SLOT 1 PORT 2’. The Windows Firewall on node is not properly configured for failover clustering. The other day I was pulling hair from my head trying to configure a Windows Failover Cluster intended for an SQL Server Availability Group setup.ĭuring the cluster validation stage I always got this message:
0 kommentar(er)
