The transition protocols are all disabled in Windows 10 1803, so I guess Microsoft don't need them anymore.
We've disabled all the transition protocols (ISATAP, Teredo, etc) since Windows 7, leaving only native IPv6 (but the campus isn't IPv6 enabled). Never had any problems.
-----Original Message-----
From: Support issues for windows in UK HE & FE <[log in to unmask]> On Behalf Of Alexandre Cop (Staff)
Sent: 22 May 2018 10:42
To: [log in to unmask]
Subject: Disabling IPv6 on clients
Hi all,
We're investigating some odd behaviours/lags in our estate at the moment, and we are wondering whether we're seeing timeouts related to name resolution.
One question that came up recently was whether we should disable IPv6 on the client side, given that we don't route it.
I seem to recall that Microsoft was not in favour of doing so in Windows 7, and I'm not even sure if it's possible in Windows 10.
What is your experience? Do you:
- Disable IPv6
- Route IPv6 internally
- Have some magic settings that makes IPv6 behave (instead of the potential risk of having packets going down the IPv6 ether)
Thanks!
Regards,
... Alex ...
Alexandre Cop
Windows Product Engineer
UoD IT, University of Dundee
The University of Dundee is a registered Scottish Charity, No: SC015096
[University of Central Lancashire 1828 - 2018]
Please consider the environment before printing
|