comp/net virus protection

[mbpark]

TW,

I did post why that command (netsh winsock reset) works in great detail. It's one of the enhancements MS added to XP SP2 for consumers to fix a large problem with spyware attaching itself to the TCP/IP stack by replacing the Winsock (TCP/IP) stack with a known good set of settings.

Originally Posted by tw

Then ask details so that the next reply adds new information. Otherwise spend $70 per hour and learn nothing.

Only reason to fix things is to learn. If the solution is posted and not understood, then ask or quit. Those are the two options. Therefore learn or not learn.

Most every reason for doing those things (netsh winsock reset) were never provided - intentionally. If not done, then one does not learn why they were so critically important. But again, fix things first and foremost to learn. Or stay ignorant and pay someone $70 per hour to do what is not really complex. It only looks complex because it is unknown.

Again the point because so many are bad at problem analysis. Don't try to fix it immediately. First objective is to only learn what is wrong. Fixing comes much later. Those who never fixed things always want instant solutions. Rarely learn how to break problems - even non-technical problems - down into parts.

Command prompt is where Shawnee entered "netsh winsock ..." IPCONFIG is also entered there. You would not know that if you had not yet done what Shawnee did. If you also do not do it (if you only read), then you also do not learn anything.

I never used that "netsh ... " option. So I too did what mbpark recommended. Why? Otherwise I also would have no idea what he posted. To learn means 1) all those actions must be performed, 2) all those questions answered, and 3) anything not understood requires asking for details. Only other option is to quit and learn nothing.

Furthermore, its a two way street. All parties (not just Shawnee) learn from the experience.