IPv6 not activated

Page 2 of 2 FirstFirst 12

  1. Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       #11

    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.
      My Computer


  2. Posts : 607
    7 x64 Ultimate
       #12

    [QUOTE=tbernstein;460751]
    aem said:
    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.
      My Computer


  3. Posts : 2
    Windows 7
       #13

    tbernstein - your solution worked like a charm <S>

    Tks & Happy Holidays!

    EVGA i680 MB w NVidiea network adapter and Win 7 (64 bit)
    Last edited by Canuck4ever; 26 Dec 2009 at 16:02. Reason: added specs
      My Computer


  4. Posts : 106
    Win 7
       #14

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

    Terry
      My Computer


  5. Posts : 1
    win 7
       #15

    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.
    Last edited by TheRev; 14 Mar 2010 at 21:39. Reason: dyslexic fingers
      My Computer


  6. Posts : 13
    win7 ultimate x64
       #16

    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??
      My Computer


  7. Posts : 1,216
    Windows 7 Ultimate 64-bit
       #17

    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.
      My Computer


  8. Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       #18

    benjy206 said:
    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.
    IPv6

    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?
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:28.
Find Us