Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface.Type any one of the following values in the Value data: field to configure the IPv6 protocol to the desired state, and then click OK: Type DisabledComponents, and then press ENTER. In the Edit menu, point to New, and then click DWORD (32-bit) Value. Note: If the DisabledComponents entry is unavailable, you must create it. In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\ParametersÄouble-click DisabledComponents to modify the DisabledComponents entry. This KB article tells us about a setting that affects what Windows prefers, emphasized in bold: Hmm, we have to look at the DNS settings of Windows. # localhost name resolution is handled within DNS itself. Type %WINDIR%\System32\Drivers\Etc\Hosts. Okay, so, where does it come from, let's look at the hosts file. Thus Windows prefers to use the IPv6 loop back IP address ::1 (see RFC 2373) as it is listed first. Looking up localhost using nslookup gives us: localhost is traditionally a TLD (see RFC 2606) which points back to the loop back IP address (for IPv4, see RFC 3330, especially 127.0.0.0/8). You might still wonder why localhost is resolving to ::1, while traditionally we would expect it to resolve to the IPv4 address 127.0.0.1. So, the ping packets don't pass through any physical network interface only through a virtual loop back interface which directly sends the packets from port to port without any physical hops. Your localhost is used to refer to your computer from its "internal" IP, not from any "external" IPs of your computer. You are not pinging the same interface, without any physical interfaces you still have a "local host".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |