Up to now, we have been running a fairly large peer-to-peer network of almost 100% Windows 10 Pro workstations with ONLY IPv4 enabled on the workstation NICs. (There are 3 interconnected subnets with no name service shared between them). Disabling IPv6 was done historically because using IPv6 in addition to IPv4 caused problems.
Yet, more often now, Experts advise enabling IPv6. Going along seemed perhaps a good idea. And, in the sense of "if it ain't broke don't fix it", the hoped-for fix was to fix the Network list of computers in each distinct subnet - which has become more flaky/unreliable. The experience with this was mixed as not all computers were switched to IPv6; i.e. not all subnets' workstations had IPv6 enabled.
We have since solved the Network computer name list problem. So, there's a decision to make:
- "if it ain't broke, don't fix it" says to leave only IPv4 enabled.
- Expert advice says to also enable IPv6.
It surely appears that "IPV6" in Windows is NOT simply an addressing scheme but also carries with it other things - things which I'm unable to list, but one hopes.
I have not had any trouble that I know of in enabling IPv6. Yet, when one of the senior folks enables it on his own workstation, the network connectivity dies. This problem survives a reboot and, yes, IPv4 remains enabled.
I believe it's bad practice to have a mix of settings in a network. So if someone can suggest a fix to the network connectivity problem then perhaps we can move forward to IPv6. Otherwise, I'll likely have to revert to IPv4 ONLY throughout to maintain consistency.