Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

I did some commands in CMD now firefox wont work at all!

  • 1 antwoord
  • 1 heeft dit probleem
  • 4 weergaven
  • Laatste antwoord van cor-el

more options

So my problem was I couldn't ping IP addresses. So I looked up a tutorial I followed this EXACT thing and now I can't connect firefox everything says its connecting but it never loads no error message nothing. Here is exactly what I did that now gave me this problem.

resets the ipv4 interface

netsh interface ip reset

flush and reregister DNs

ipconfig flushdns net stop dnscache net start dnscache ipconfig /registerdns

clear persistent routes
route print -f
:: start / restart mrxdav
net stop netbt
net stop mrxdav 2>nul
net start mrxdav
net start netbt
::  clean the arpcache
arp -a -d 
 :: I might have the order of the switches backwards and the order matters, so if that doesnt do anything put the -d before the -a
:: make sure winhttp and webclient  services are running (this is a mystery to me / neither appear necessary, but both have fixed my problem on various occasions)
net start webclient
net start winhttp
So my problem was I couldn't ping IP addresses. So I looked up a tutorial I followed this EXACT thing and now I can't connect firefox everything says its connecting but it never loads no error message nothing. Here is exactly what I did that now gave me this problem. :: resets the ipv4 interface netsh interface ip reset :: flush and reregister DNs ipconfig flushdns net stop dnscache net start dnscache ipconfig /registerdns :: clear persistent routes route print -f :: start / restart mrxdav net stop netbt net stop mrxdav 2>nul net start mrxdav net start netbt :: clean the arpcache arp -a -d :: I might have the order of the switches backwards and the order matters, so if that doesnt do anything put the -d before the -a :: make sure winhttp and webclient services are running (this is a mystery to me / neither appear necessary, but both have fixed my problem on various occasions) net start webclient net start winhttp

Alle antwoorden (1)

more options

Best would be to ask advice at a Windows oriented forum if you have broken your internet connection.