netsh int ip reset worked...

[JP56]

I had a problem where shutdown took an age, web browsing dropped to a crawl and I was unable to reach most websites.

I could reach and open files on my local network NAS drive fine but COULD NOT do the following: connect to my router or any other node on my local network 192.168.1.* , or login to my router.

I COULD ping my local network
I COULD tracert a remote website by url or IP address...

So, I figured it's a TCP/IP problem.

Issuing the "netsh int ip reset" and "netsh winsock reset catalog" commands cured the problem immediately

MY QUESTION is: Fixing the problem is one thing, but what would have been the likely CAUSE of the problem, and what action is recommended if it becomes something I have to do more often? Thanks!

 

[shags72]

Seems like there is a lot of that going on in windows 8 and 8.1 and it seems to fix a lot of things too. I would like to know also!

 

[JP56]

C'mon guys... someone must have some insight into this question...yeah?

Corrupt stack - causes? Is it Win 8 / 8.1 at the root? Or what? Opinions or experiences please...

BTW, based on clean scans with Bitdefender, SAS, MBAM, MBAR, HitmanPro etc, my system is (and always has been (except for cookies...thanks SAS)) clean of malware...

So... the cause? Eh? Ta!