Ping: Transmission failed. general failure

igolovin2012-03-26 11:00:39

Ping

igolovin, 2012-03-26 11:00:39

Windows 7, Professional 64. The network suddenly stopped working.

ipconfig shows that the computer has an ip that is already on the network and is assigned an ip address that seems to the system to be correct. The address has changed several times. The result is the same.

ping anything other than localhost gives "Ping: Transmission failed. General failure"

Tried netsh int ip reset and netsh winsock reset - didn't help.

The firewall is disabled. Antivirus - Avast. Turned it off, same result.

How, exactly, to deal with this muck?

Answer the question

In order to leave comments, you need to log in

11 answer(s)

Fenja, 2012-03-26
@Fenja

We try to reset winscock and tcp / ip with the commands
netsh int ip reset
netsh winsock reset

svfoster, 2012-03-26
@svfoster

The first thing that comes to mind is to try System Restore for the date when everything worked.
If the hardware is intact, this usually helps.

cat_crash, 2012-03-26
@cat_crash

Have you played with network drivers? Try updating / resetting to default settings / flashing (if possible)

Danil Shirokikh, 2013-11-11
@DanilShirokikh

there was the same situation - I tried everything that is written - restarting everything that is possible, cutting off ipv6, looking for sudden new devices, but as it turned out, it was in dhcp. I set a static ip address and it worked.

igolovin, 2012-03-26
@igolovin

network card is built-in. Therefore, you won’t fight much there. I thought maybe the network card died. Booted into live-cd Ubuntu - everything works.

rasa, 2012-03-26
@rasa

Have you tried safe mode with network drivers loaded?

S1ashka, 2012-03-26
@S1ashka

in properties of connection any superfluous protocols\services are not established?
Are you entering the address manually?
and the localhost responds?

Aldorr, 2012-03-26
@Aldorr

Nothing can be done here without ipconfig / all, nslookup and sfc /scannow outputs.
Publish reports to the studio

Sweng, 2014-08-18
@Sweng

Let the answer remain, you never know who stumbles upon the search: disabling NLB in the connection properties can help.

JustSoul, 2017-07-06
@JustSoul

So, the solution to the problem:
Go to Start-> Run and enter the mmc command. The console will open, where you need to go to File-> Add or remove snap-in. In the left list, select IP Security Policy Management, Add, Done, OK. Now we see that the snap-in we added has appeared in the root of the console. Open it and remove all elements from it.
Taken from here .

topordon, 2018-05-15
@topordon

None of the above helped me, as it turned out, the firewall blocked everything, added the necessary address to the exceptions and that's it