6to4 disabled by default on W7SP1

Dan Wing dwing at cisco.com
Fri Sep 2 01:44:42 CEST 2011


> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de [mailto:ipv6-
> ops-bounces+dwing=cisco.com at lists.cluenet.de] On Behalf Of Phil Mayers
> Sent: Thursday, September 01, 2011 6:58 AM
> To: ipv6-ops at lists.cluenet.de
> Subject: Re: 6to4 disabled by default on W7SP1
> 
> On 01/09/11 13:26, Bernhard Schmidt wrote:
> > Hi,
> >
> >> This was my impression until recently too; I thought that, by
> default,
> >> AD members with "client" role had 6to4 disabled, with Teredo and
> ISATAP
> >> enabled.
> >
> > It's the other way around, Teredo is disabled in "Enterprise"
> clients,
> > 6to4 and ISATAP are enabled ("Enterprise" client meaning joined to an
> > AD). You have to do specific configuration to enable Teredo in this
> > environment.
> 
> Interesting. Is this documented somewhere or are you going on
> observation?
> 
> 
> FYI we've recently explicitly disabled all 3 transition technologies
> (Teredo, 6to4, ISATAP) via group policy at our site. Confusingly, the
> output of "ipconfig /all" now shows:
> 
> 6to4 adapter: completely absent from output
> Teredo/ISATAP: show "Media disconnected"
> 
> ...the latter of course not being very helpful at all.

http://support.microsoft.com/kb/929852 describes bit values in the 
Windows registry to disable IPv6 tunneling interfaces, native IPv6 
interfaces, and prefer IPv4 over IPv6.  

-d





More information about the ipv6-ops mailing list