IPv6 not activated

[cazeault]

hence Home group cannot be set up. We have 3 computers at home and all are on Win7 Ultimate. The HomeGroup worked 1 day and then after a reboot, it saus that it cannot connect to such a group because Teredo IPv6 is not activated. The network on all threee is MSHOME.

If I look in the network paramaters IPv4 is ther activate dand working , IPv7 is there also "not activated". But I do not know how to change it....

Otherwise mail, surf etc everything is OK. I use BitDefender 2010 suite, activated correctly, UNP working OK etc.. no problem there.

Anyone have an idea???

Thanks Henri

 

[logicearth]

Did you have BitDefender when it was working for that 1 day?

 

[cazeault]

Home groupe

I bought BitDefebder for all 3 computer the day after that

 

[aem]

Is it showing in ipconfig?

Check if there is an entry called
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

If so delete it.

 

[cazeault]

I deleted

the entry name "...... disabled" and pnlu remains the entry "..... activated" Now I will try to setup the home groupe adn revert back

Thanhs henri

 

[cazeault]

On computer A (Medion portable) ipv6 is activated and I can access the work group. On the netbook B, ipv6 does not appear and ont on IPconfig; upstairs on the Dell the IPv6 is there but not activated (ipconfig says that it is there but nothing near on the same line

Henri

 

[aem]

So what did you need to do?

 

[cazeault]

I just want that my 3 computers connect to the homegrou

but it says that if IPv6 is not working or not activated , hence it can join the group.

Up to now, only one computer (n° 1) can join the group it initiated itself;

The second one do not show any ipv6 and the 3rd one show the IPv6 but nothing that says it can join the group (aside (n° 2 and n° 3 says the same) : IPv6 must be activated to create or join a homegroup...

Henri all 3 computer belong to a network named "MSHOME"

 

[zigzag3143]

but it says that if IPv6 is not working or not activated , hence it can join the group.

Up to now, only one computer (n° 1) can join the group it initiated itself;

The second one do not show any ipv6 and the 3rd one show the IPv6 but nothing that says it can join the group (aside (n° 2 and n° 3 says the same) : IPv6 must be activated to create or join a homegroup...

Henri all 3 computer belong to a network named "MSHOME"

Can I ask an obvious question?

why not just setup a "workgroup" based network and not have to deal with either IPv6 or homegroup both of which are notoriously flaky?

Ken J+

 

[tbernstein]

Is it showing in ipconfig?

Check if there is an entry called
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

If so delete it.

Sorry, but just the opposite.
I found the solution in the MS knowledgebase and used it so sort out my own system. And posted it here a few weeks back. There are also other posts saying the same thing.

regedit
hkey-local machine\system\currentcontrolset\services\tcpip6\parameters\...
Then you have to set the DisabledComponents Dword to 0
And if there isn't a disabledcomponents dword you have to create one and then set it to zero

It seems that if there is no disabledcomponents dword value 0 Windows 7 assumes a positive value. Which sounds quite like a bug to me. But there you go.

 

[chev65]

Want my advice, get rid of bit defender and all other AV software. In the end, they cause more problems than they solve. The fact that you installed Bit Defender after you got your Homegroup up and running was obviously a mistake. No fault on anyone's part, really just typical AV behavior.

The post above about having to change the registry settings proves my point. I certainly did not need to do any of that in order to use Homegroup networking on any of my machines. It's worked absolutely flawlessy since day one in fact.

There is no way on earth that the default registry settings would have this value incorrect unless the user installed something, such as an AV product, to set it that way in the first place. When you change that registry setting you are only undoing what your AV software has done.

The Op is unknowningly solving his own problem by saying this> Quote: I bought BitDefebder for all 3 computers the day after that, meaning the day after he set up Homegroup. Hmmm and then the next day Homegroups suddenly stopped working? I mean come on people, how obvious is this?

I think we need to get off the blaming Windows 7 for mystery problems bus and get back to reality here.

 

[RogerR]

And if there isn't a disabledcomponents dword you have to create one and then set it to zero

FWIW; I have tried it both ways and IPv6 was reported as working in both instances and Homegroup is not working on my x64 machine. By contrast, the two x32 systems fired up Homegroup right out of the box.

All are running AVG anti-virus.

 

[Canuck4ever]

tbernstein - your solution worked like a charm <S>

Tks & Happy Holidays!

EVGA i680 MB w NVidiea network adapter and Win 7 (64 bit)

 

[tbernstein]

Thanks, ( and I still think it's a bug!)

Terry

 

[TheRev]

IP6 activation

Thank you, this finally worked for me; however, as precaution I also updated the firmware on my router in case it did not recognise IP6. A reset of the PC is also a good start to ensure that IP6 is enabled. Another block is Zone Alarm, apparently it doesn't like IP6.

 

[stick666]

hi there im tryng to connect to my net service via wirelless on my desktop and when i connect it says my ip6 dosent conects to network ; this problem started 2 days ago.

conectivaty ipv4: internet \ conectivaty ipv6: no acsses to network

windons cant detect auto the ipv6

using windowns 7 ultimate what can i do??

 

[benjy206]

IPv6 isn't running yet i thought so why is everyone going on about IPv6, your router doesn't support IPv6 infact we are a long way from it? You may have you ip address for v6 but it doesn't make a difference it's not running.

 

[chev65]

IPv6 isn't running yet i thought so why is everyone going on about IPv6, your router doesn't support IPv6 infact we are a long way from it? You may have you ip address for v6 but it doesn't make a difference it's not running.

There are currently many Windows services using IPv6 on the LAN, Homegroups being one of those that requires IPv6 in order to work at all. And yes, most every single router made in the last 10 years does in fact support the IPv6 protocol.

Here is how you would fix this problem to get Homegroups working again. Been there done that.
http://www.sevenforums.com/network-sharing/116810-ipv6.html#post1003900

As for IPv6, here is some info about why it should be not disabled and what exactly it's used for since it's not yet being used to access the internet.

The Argument against Disabling IPv6.

It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx

Still think that IPv6 isn't used for anything?