Can't ping localhost over IPv4 only IPv6

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 7 Ultimate x64
       #1

    Can't ping localhost over IPv4 only IPv6


    I am trying to get to the bottom of several networking issues, but just been thrown a curve-ball - so hoping someone can help.

    I have a BT HomeHub v2 acting as Firewall and DHCP
    I have a QNAP NAS and several devices (mostly Windows 7 and iOS devices)

    The vast majority of my networking setup seems OK - however on one Windows 7 laptop I am having problems.

    The Laptop can 'see' remote shares, access the Internet and ping other devices on the network - however remote devices cannot ping the laptop.

    Whilst trying to ascertain what could be the cause I thought that I would ping 'localhost' on the laptop - after all, it should be able to see itself!

    If I force ping using the loopback address, then this is my result

    Code:
    C:\Users\david>ping 127.0.0.1
    
    C:\Users\david>ping 127.0.0.1
    
    Pinging 127.0.0.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    
    Ping statistics for 127.0.0.1:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    However, if I try with forcing it to IPv6 then I get,

    Code:
    C:\Users\david>ping localhost -6
    
    Pinging London [::1] with 32 bytes of data:
    Reply from ::1: time<1ms
    Reply from ::1: time<1ms
    Reply from ::1: time<1ms
    Reply from ::1: time<1ms
    
    Ping statistics for ::1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    Why is it that I can ping using IPv6 and not IPv4? Could this be the cause of my issues. I.E the fact that other devices cannot ping the laptop.

    As far as I know I have not set anything up differently.
      My Computer


  2. Posts : 391
    Windows 7 Professional x64 Backtrack 4 R2
       #2

    Firstly make sure IPv4 is checked under control panel > network and sharing center > change adapter settings > right click the adapter used for connectivity and select properties.

    To be safe renew your DHCP address :

    ipconfig /release
    ipconfig /renew

    Also could you post the results of an ipconfig /all ?

    Thanks
      My Computer


  3. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #3

    IPv4 was all checked, and working as I could ping the default router, but not the localhost.

    I found a part resolution with running the command:
    Code:
    netsh interface ipv4 reset
    Which effectively resets all the IPv4 settings.

    So now, I can ping localhost, and all works. Which is good.
    Just that I am back to my original problem, nothing else on the network can ping the laptop.
      My Computer


  4. Posts : 391
    Windows 7 Professional x64 Backtrack 4 R2
       #4

    Believe it or not,resetting the TCP/IP stack was my going to be my suggestion for your localhost problem. Though it would still be useful if you could post the results of the ipconfig /all command.

    I would suggest going to the following website and following the instructions to enable ping.
      My Computer


  5. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Thanks Clinkz. I have followed the advice in that link, and created an inbound rule for Ping Requests. I have also tried after disabling the firewall.

    Below is the results of ipconfig /all
    Code:
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : London
       Primary Dns Suffix  . . . . . . . : 
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home
    
    Wireless LAN adapter Wireless Network Connection 6:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #5
       Physical Address. . . . . . . . . : 00-27-10-B1-18-75
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Wireless LAN adapter Wireless Network Connection:
    
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6200 AGN
       Physical Address. . . . . . . . . : 00-27-10-B1-18-74
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::51c9:e797:2c56:5d02%27(Preferred) 
       IPv4 Address. . . . . . . . . . . : 192.168.1.93(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 15 April 2011 08:41:03
       Lease Expires . . . . . . . . . . : 16 April 2011 08:41:16
       Default Gateway . . . . . . . . . : 192.168.1.254
       DHCP Server . . . . . . . . . . . : 192.168.1.254
       DHCPv6 IAID . . . . . . . . . . . : 738207504
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-53-53-A7-5C-26-0A-13-43-AE
       DNS Servers . . . . . . . . . . . : 192.168.1.254
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Local Area Connection* 13:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : xmpie.com
       Description . . . . . . . . . . . : Check Point Virtual Network Adapter For Endpoint VPN Client
       Physical Address. . . . . . . . . : 54-43-2D-2B-A5-15
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Local Area Connection* 12:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Check Point Virtual Network Adapter For SSL Network Extender
       Physical Address. . . . . . . . . : 54-B8-02-C3-26-13
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Bluetooth Network Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : 5C-AC-4C-FD-5A-B1
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Local Area Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Intel(R) 82577LM Gigabit Network Connection
       Physical Address. . . . . . . . . : 5C-26-0A-13-43-AE
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{1473E993-6FAC-4925-83B7-1626AF414F5D}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{11869B56-9918-48EC-878C-43EDACC53C2E}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{8A2E224C-9740-4902-B0F0-0223CD6FE4AF}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:49c:1dbd:a967:b970(Preferred) 
       Link-local IPv6 Address . . . . . : fe80::49c:1dbd:a967:b970%14(Preferred) 
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled
    
    Tunnel adapter isatap.xmpie.com:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.home:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #6
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
      My Computer


  6. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #6

    This issue is back to haunt me. I need to Remote Desktop into this Window 7 laptop (same as the OP), but I cannot establish a connection. All the Remote Desktop option are correctly set - but I still cannot PING the laptop from another server on the same network, although the laptop can ping the server!

    This is incredibly frustrating, as I seem to be allowed outbound connection (Ping, RDP, UPNP etc.) but nothing seems to be getting back in. I have disabled the firewall as well, but this has no effect.

    Anyone have any ideas?
      My Computer


  7. Posts : 2,528
    Windows 10 Pro x64
       #7

    Try disabling the 6to4, Teredo, and ISATAP adapters on both hosts - if you aren't using anything that requires IPv6 and/or IPHTTPS (like DirectAccess), you can do this safely:
    Code:
    netsh interface 6to4 set state state=disabled
    netsh interface isatap set state state=disabled
    netsh interface teredo set state state=disabled
    ipconfig /flushdns
    ipconfig /registerdns
    These 5 commands (you'll need an elevated cmd prompt on Win7 or 2008R2 to execute these commands successfully) will disable a machine's ability to go out to the internet and get a public IPv6 address, and then (hopefully, within 15 minutes) register the IPv4 address it is using with the DNS server it's configured to use on your domain. If you do the above, wait 15 minutes, and try to ping again, you should be able to ping (and it should work) IPv4 addresses on each end.
      My Computer


  8. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #8

    Thanks for the input cluberti. I disabled all those, and run the commands. Rebooted, left it 15 minutes, but still cannot ping the laptop from any other device on the same network, although the laptop can ping the others.
      My Computer


  9. Posts : 2,528
    Windows 10 Pro x64
       #9

    After running those commands, can you post the IP configuration from ipconfig on the laptop and also from another device on the network that you're trying to access? It'd be interesting to see what you've got (remove anything incriminating as necessary ).
      My Computer


  10. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #10

    OK - After talking it through with another individual, I uninstalled all the network adapters, re-installed, and reset the TCP/IP Stack - so I back at a default config, that should work!

    For the sake of this I am using two platforms:
    • Windows 7 Professional Latpop - called 'LONDON'
    • Windows 7 Ultimate Desktop PC - called 'PRAGUE'


    The IPCONFIG from 'Prague' is ...
    Code:
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . : home
       Link-local IPv6 Address . . . . . : fe80::c579:2fea:585e:2a4a%10
       IPv4 Address. . . . . . . . . . . : 192.168.1.120
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
    
    Tunnel adapter Local Area Connection* 11:
    
       Connection-specific DNS Suffix  . : 
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:100a:3574:a964:c437
       Link-local IPv6 Address . . . . . : fe80::100a:3574:a964:c437%11
       Default Gateway . . . . . . . . . : ::
    
    Tunnel adapter isatap.home:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home
    The IPCONFIG from 'London' is

    Code:
    Wireless LAN adapter Wireless Network Connection 6:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
    
    Wireless LAN adapter Wireless Network Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . : home
       Link-local IPv6 Address . . . . . : fe80::391f:8f25:1768:733b%20
       IPv4 Address. . . . . . . . . . . : 192.168.1.64
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
    
    Ethernet adapter Bluetooth Network Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
    
    Ethernet adapter Local Area Connection* 13:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : {{REMOVED MY OP}}
    
    Ethernet adapter Local Area Connection* 11:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
    Whilst on the laptop, 'London' I can ping 'Prague' fine, both using IPv4 and IPv6
    Code:
    C:\Users\david>ping prague
    
    Pinging PRAGUE.home [192.168.1.120] with 32 bytes of data:
    Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.120: bytes=32 time=1ms TTL=128
    
    Ping statistics for 192.168.1.120:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 1ms, Average = 1ms
    
    C:\Users\david>ping prague -6
    
    Pinging Prague [fe80::c579:2fea:585e:2a4a%20] with 32 bytes of data:
    Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
    Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
    Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
    Reply from fe80::c579:2fea:585e:2a4a%20: time<1ms
    
    Ping statistics for fe80::c579:2fea:585e:2a4a%20:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    But when on the PC, 'Prague'
    Code:
    C:\Users\david>ping london
    
    Pinging london.home [192.168.1.64] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    
    Ping statistics for 192.168.1.64:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    
    C:\Users\david>ping london -6
    
    Pinging London [fe80::391f:8f25:1768:733b%10] with 32 bytes of data:
    Reply from fe80::391f:8f25:1768:733b%10: time<1ms
    Reply from fe80::391f:8f25:1768:733b%10: time<1ms
    Reply from fe80::391f:8f25:1768:733b%10: time<1ms
    Reply from fe80::391f:8f25:1768:733b%10: time<1ms
    
    Ping statistics for fe80::391f:8f25:1768:733b%10:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    The same is true if I try to remote desktop into the laptop, 'London'. I can do it whilst using a IPv6 address, but not when it defaults to IPv4.

    I have never seen it when IPv4 fails, when IPv6 succeeds. What is going on with my IPv4 traffic?
      My Computer


 
Page 1 of 3 123 LastLast

  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 01:34.
Find Us