NLB on Window 2019 Server (Standard) and Vmware

MandyCAP 101 Reputation points

Hi all,

I've ran out ideas and needs some help.

We are using NLB in multicast mode - and its working fine (for HTTP) - but we are a bit perplexed that its not possible for the nodes within the cluster to simply ping the cluster IP address.
We have a situation where the monitoring process which lives on the member nodes needs to be able to ping to show its in a happy state……

Would you expect it to work? We have this environment happily working on Windows 2016 with the same monitoring process and VMWare.

Just illustrate it in more detail:
We have 4 cluster member servers.
These are all in an NLB cluster with the cluster IP. (cluster subnet (Cluster Param populated with IP add, subnet, full internet name and network address. Multicast is checked. Port Rules ae on 80 and 443 (tcp | multiple))
You can ping the cluster IP from outside of the cluster - no problem - as you would expect.
It's not possible to ping the cluster IP from any of the four cluster member servers.

Any thoughts?

I'm pondering if there's a bug in Windows 2019.

thanks all

Windows Network
Windows Network
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Network: A group of devices that communicate either wirelessly or via a physical connection.
483 questions
{count} votes

Accepted answer
  1. MandyCAP 101 Reputation points

    Turns out the issue related to the version of FortiClient we were one. We were running 6.4.2, upgraded to 6.4.6 and it resolved the issue.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful