Hello there,
This behavior is by design. It occurs because NetBIOS no longer binds to IP address resources in Windows Server 2016 or later versions of the Windows Server-based Cluster service.
To work around this behavior, use the Cluster Management console to determine the name of the IP address resource that must be changed.
NetBIOS and WINS don't bind to cluster IP address resources https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/netbios-wins-dont-bind-cluster-ip-address-resources
----------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer–