3 ms·
https://www.google.com/#q=winsock+reset https://www.google.com/#q=winsock+reset No, it's not as rare as you think. Yes, it's because of the lousy design of the
by taiki 13y ago
https://www.google.com/#q=winsock+reset https://www.google.com/#q=winsock+reset
No, it's not as rare as you think. Yes, it's because of the lousy design of the TCP/IP stack in windows.
- nbevans 13y agoYes it is. No it isn't. Yes it is. No it isn't. Repetitive much? There's nothing wrong with the network stack in Windows. NT has always had a first class network stack and they keep improving it with every release, as is normal for any modern mainstream OS. PS: That Google link I assume was provided for humour rather than any real substance. Two can play at that game: https://www.google.co.uk/?q=osx+network+reset https://www.google.co.uk/?q=osx+network+reset https://www.google.co.uk/?q=linux+network+reset+defaults https://www.google.co.uk/?q=linux+network+reset+defaults
- taiki 13y agoThat's resetting settings. What netsh winsock reset does is tear out DLLs, tear out various registry settings and mucks about with other system files. Clearly you have no idea what you're talking about.
- nbevans 13y agoThis describes perfectly what a Winsock reset performs and it doesn't exactly correlate with your FUD: http://support.microsoft.com/kb/299357 http://support.microsoft.com/kb/299357 So there is no real distinction here between a Winsock reset and the equivalent operations in the other 2 big OSes. The difference is that whilst Windows holds its network configuration in the Registry (ugh), the other two do not. The operations being performed is otherwise pretty much identical.