IPv6 "infecting" windows networks when a specific PC joins them


  1. Posts : 3
    windows 7 pro 32 and 64 bit
       #1

    IPv6 "infecting" windows networks when a specific PC joins them


    I have a set of PCs which if connected to a windows network will make all computers on that network default to ipv6 when resolving names. This happens even if IPv6 is unchecked, if the ipv4 binding is set above 6 in the advanced properties of the network card. If any of these PCs joins a network with a point of sale system (Aloha) that system develops problems since Aloha does not like IPv6. At all. All computers including the aloha terms are Win7, 32 or 64 bit.

    Reproduced this with different routers and network topologies.

    For example, I take one of these particular PCs to my home network. Prior to the terminal going onto the network
    ping localhost --> 127.0.0.1
    ping computername --> 192.x.x.x

    After the PC has joined the network, just attached to the same router, not on the same workgroup, etc., now all computers on the network return

    ping localhost --> ::1
    ping computername --> 08fe:xxxx (IPv6 address)
    ping computername -4 --> 192.x.x.x
    ping localhost -4 --> 192.x.x.x

    This behavior continues even without IPv6 enabled on any adapter on the network. When the PC is removed from the network, all other PCs continue with the new behavior.

    I have tried netsh winsock reset, net stop dnscache, netsh int ip reset.log hit, unchecking IPv6 in multiple places, ensuring binding order has IPv4 above IPv6 on all network adapters (none hidden) etc. It's like this PC infects other windows PCs with IPv6 ...

    I have not tried disabling IPv6 from the registry or by Policy in my lab but I believe I tried this on previous network with no affect. Any thoughts appreciated
      My Computer


  2. Posts : 3
    windows 7 pro 32 and 64 bit
    Thread Starter
       #2

    Issue solved! See MS KB How to disable IP version 6 (IPv6) or its specific components in Windows 7, in Windows Vista, in Windows Server 2008 R2, and in Windows Server 2008

    Specifically, if the HKLM\system\currentcontrolset\services\tcpv6\parameters\disabledcomponents is not set to DWORD 0xFFFFFFFF then this behavior can occur.

    The above key is from memory, see the MS KB for detailed information.
      My Computer


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

    360fish said:
    Issue solved! See MS KB How to disable IP version 6 (IPv6) or its specific components in Windows 7, in Windows Vista, in Windows Server 2008 R2, and in Windows Server 2008

    Specifically, if the HKLM\system\currentcontrolset\services\tcpv6\parameters\disabledcomponents is not set to DWORD 0xFFFFFFFF then this behavior can occur.

    The above key is from memory, see the MS KB for detailed information.

    You should be aware that when you disable IPv6 certain components of Windows networking will not work correctly.

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


  4. Posts : 3
    windows 7 pro 32 and 64 bit
    Thread Starter
       #4

    Chev65 thank you for your thoughtful reply. I have two issues with IPv6 - #1 the vendor I use for Point of sale, NCR / Aloha recommends disabling IPv6 in its build documentation for both front of house touchscreens and back of house servers. More importantly, this behavior I saw where IPv6 takes over IPv4 as the primary ... transport? as described in my OP where things like pings return IPv6 information unless I force the ping with -4.

    This behavior spreads from computer to computer if one mis-configured machine joins the network (just the workgroup) then all machines on the network start 'defaulting' to this behavior.

    The point of sale system uses very simple networking, Netbios must be forced on for all clients, no DNS no domain all data runs from shared folders. In this situation any change to the default network behavior causes dramatic, or subtle, issues with the software
      My Computer


 

  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 20:58.
Find Us