This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 5%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
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 255.255.0.0). (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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 73%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESQ%3C/text%3E%3C/svg%3E)
This is a quick note to let you know that I am currently performing research on this issue and I will perform a test in my lab. I will get back to you as soon as possible. I appreciate your patience.
If you have any updates during this process, please feel free to let me know.
Hi Sunny,
Just wondering how you got on with your testing? Were you able to replicate the issue?
Regards
Mandy
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.