svchost trying to connect to IPv6 even that IPv6 is disabled

Page 2 of 2 FirstFirst 12

  1. Posts : 286
    Linux:Debian, Kali.. 2xWin8.1,2x,1x7Pro, Retro:1x2003server.1xXPpro, 1xW2k,1x98SE,1x95,1x3.11
    Thread Starter
       #11

    Digital Life said:
    If it's any consolation for you " ::1 localhost " will not pass through your computer to your network, Every computer has that same IP.
    Yes i know, it's the same with 127.0.0.1 and those addresses shouldn't be visible in the system monitor, and it isn't. But it was worth to try it anyway.
    I don't understand why ipv6 addresses appear. I must have missed something somewhere.
    I have disabled ipv6 on all my win7 computers years ago and i have no ipv6 addresses on them. So i know it is possible to disable ipv6. but it just don't work on this win8.1 machine, so i must have missed something.. but what..
      My Computer


  2. Posts : 2,798
    Windows 7 x64, Vista x64, 8.1 smartphone
       #12

    Marie SWE said:

    I even did a really unorthodox test.. i did a backup on the registry and then ripped out everything with the name IPv6 or ip6 guts and all... believe it or not, but the damned ipv6 addresses appeared anyway in the system monitor.. I did expect the system to crach or the network not working... but noooo eweryting worked even the ipv6 addresses.
    Then with certainty it is not a registry issue. It could be a device driver configuration, or a startup service.

    BTW, you don't need multiple copies of ISATAP driver. Delete them all, and one would probably re-generate on new boot. (The ISATAP driver allows IPv6 traffic to use an IPv4 network.)
      My Computer


  3. Posts : 286
    Linux:Debian, Kali.. 2xWin8.1,2x,1x7Pro, Retro:1x2003server.1xXPpro, 1xW2k,1x98SE,1x95,1x3.11
    Thread Starter
       #13

    iko22 said:
    Then with certainty it is not a registry issue. It could be a device driver configuration, or a startup service.

    BTW, you don't need multiple copies of ISATAP driver. Delete them all, and one would probably re-generate on new boot. (The ISATAP driver allows IPv6 traffic to use an IPv4 network.)
    I have deleted them too and still i get ipv6 addresses
    The next step I am doing now is to look up system files that contain settings for ipv6 and also ipv6 dll files.
    Fortunately, I have the system recovery discs if I tear apart the system too much. *HaHaHa*

    But this dissection of the system's IPv6 may be of use to someone else in the future.

    My temporary solution until I find the solution, is that i have blocked all ipv6 protocols and addresses in the firewall.

    What I do find interesting is that the ipv6 addresses are still visible in the system monitor... While blocked ipv4 addresses are never visible there if they are blocked.
      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 03:56.
Find Us