Despite WSH’s experience. BT seem not to have fully addressed the IPv6 routing issue. Their consumer broadband rollout is still dependent on IPv4, and IPv6 support seems inconsistent across their infrastructure. My BT Smart Hub setups advertise IPv6 locally, but the addresses are link-local or ULA (unique local), meaning they don’t route properly to the wider internet. This leaves us customers with the appearance of IPv6 capability but no functional end-to-end connectivity.
My BT’s Smart Hub 2 show IPv6 addresses in Windows and router status pages.
However, the addresses are non-global (e.g., starting with fe80::, fc, or fd ), which cannot be used for public internet routing.
As a result, some Microsoft applications, like GetHelp.exe, fail when trying to connect over IPv6, even though the system reports IPv6 is “enabled.”
At the moment the tech folk at BT tell customers who call for help that the problem is with their device and to re-boot it, use a different browser and clear their browser cache. It has nothing to do with the customer’s device, It is entirely a BT network issue. They should be honest and explain that BT hasn’t fully implemented IP6 yet (in spite of what they would like us to believe) and tell their customers to disable IP6 on their devices (there is no way for the customer to disable it on the Smart Hub). Once the devices use IP4 everything works again.
Better yet they could configure the Smart Hub to disable IP6 until they’ve got it sorted.
@whs Have you tried using gethelp.exe on your IP6 routed network?
