Quote:
Originally Posted by mbpark
I did post why that command (netsh winsock reset) works in great detail.
|
But most of what you posted would not be evident to most readers unless (and maybe not until) after they had run the programs (and then came back to better learn what the catalog was).
It was actually a bad example of my point because you discussed some things that others still would not understand even after running the program. Few really would know what the TCP/IP stack is even after resetting it.
netsh involves much of the black art. I have mostly avoided netsh because so little of that program actually solved something that was not otherwise repaired by a driver reload. I will have to play with it more.
I suspect few really grasped what you had posted. But the point is that without executing those programs, one really cannot grasp them.