Ping stops responding after the first line

Question

I have a problem with the PING command on Windows 8.1. During a ping, the command returns no further output after sending the first ping request.

For example:

ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data

Thanks for your help.

EDIT 1:

I did a test with Wireshark to see what happens. Here is a screenshot. I've tried many things, but nothing has helped.

If you have any ideas ...

EDIT 2 :

I've added the result of ipconfig /all

Configuration IP de Windows

   Nom de l'hôte . . . . . . . . . . : NEPTUNE
   Suffixe DNS principal . . . . . . : xxx.xxxx.fr
   Type de noeud. . . . . . . . . .  : Hybride
   Routage IP activé . . . . . . . . : Non
   Proxy WINS activé . . . . . . . . : Non
   Liste de recherche du suffixe DNS.: xxx.xxxx.fr

Carte Ethernet vEthernet (Internal Ethernet Port Windows Phone Emulator Internal
 Switch) :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Carte Ethernet virtuelle Hyper-V #2
   Adresse physique . . . . . . . . . . . : 00-15-5D-29-83-27
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::64dd:8e3:4166:be79%19(préféré)

   Adresse d'autoconfiguration IPv4 . . . : 169.254.190.121(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.0.0
   Passerelle par défaut. . . . . . . . . :
   IAID DHCPv6 . . . . . . . . . . . : 318772573
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-17-07-94-FD-50-E5-49-3A-9A
-48
   Serveurs DNS. . .  . . . . . . . . . . : fec0:0:0:ffff::1%1
                                   fec0:0:0:ffff::2%1
                                   fec0:0:0:ffff::3%1
   NetBIOS sur Tcpip. . . . . . . . . . . : Activé

Carte Ethernet Connexion au réseau local :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Contrôleur Realtek PCIe GBE Family
   Adresse physique . . . . . . . . . . . : 50-E5-49-3A-9A-48
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.1.5(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Passerelle par défaut. . . . . . . . . : 192.168.1.254
   Serveurs DNS. . .  . . . . . . . . . . : 8.8.8.8
                                   8.8.4.4
   NetBIOS sur Tcpip. . . . . . . . . . . : Activé

Thank you in advance.

Solution

As it appears that you can't ping your own computer, the problem seems to be purely software, as the loopback interface is not passing through your network card. Either Windows has a corrupted TCP/IP stack or configuration for some reason, or something is preventing TCP/IP from correctly working (this can be a legitimate software, like an anti-virus, that for some reason is not working as it should, or it can be a malware that has severe side-effects).

You can perhaps try to reinitialize your TCP/IP stack as shown here. If still not successful, you might have to reinstall Windows.

Comments

[joeqwerty]

Your example doesn't show anything useful. Can you alaborate on your question? Do you mean that the ping target doesn't respond?

[Kevin Poirier]

My target responds from another pc. The target can be anything the command "ping" always crashes after the first line. My firewall is off.

[Philip]

Sounds like Windows might be corrupted. Have you run sfc /scannow yet?

[I say Reinstate Monica]

Can you ping yourself? (e. g. ping 127.0.0.1). If not, you've got problems on your machine with the TCP/IP stack.

[Get-HomeByFiveOClock]

Let's try to isolate the issue then. Plug in a laptop into your ethernet port and see if you can ping, if not, network; if so, then it's probably your OS or NIC. Maybe safe-mode with networking is in order?

[Joffrey]

Some questions: can you give the contents of your routing table (route print -4), also can you display a wireshark trace of the ping without the filter (i want to see dns requests)

[Cadoiz]

This usually also causes tracert to fail if someone did wonder.

[Kevin Poirier]

I no have firewall. In my screen capture wireshark, we notice that I get the ping response.

[Thomas Stinner]

These Destination unreachable ICMP messages to you are sending to Googles DNS server look very strange to me. Are you using Googles DNS Server? What does ipconfig /all show?

[Kevin Poirier]

Yes i use google dns. I add ipconfig on my first post.

[Thomas Stinner]

Maybe you have some problem with reverse DNS. Could you try a different DNS server?

[Kevin Poirier]

I do not think the problem comes from the dns. Ping reacts like if I test a local IP address.

[Kevin Poirier]

I cannot ping my computer. Same problem.

[Solrac]

I would start by reinstalling your network card drivers, if you have a faulty hardware it wont ONLY fail at ping. This is a software problem. Beign said that, if your drivers are ok then open services.msc and restart the "server" service as well as the rest of the network services... one of them could be originating the problem.

[Kevin Poirier]

I tested another profile still same problem.

[Kevin Poirier]

AAfter testing this patch microsoft, I decided to reinstall. So after reinstalling everything works again thank you.

[Ale]

@KevinPoirier ok, cool that the problem is solved!

[Cadoiz]

I edited the post because the link was deprecated. The current alternative I found is this which resolves to the link I inserted. Alternatively, you can also use the wayback machine to see a snapshot from when the site still worked. This snapshot actually looks a bit different.