Rash of Connectivity Problems

  • Thread starter Thread starter Postmandug
  • Start date Start date
P

Postmandug

OK, I've seen too many references in other posts concerning similar
problems. I'm suprised some of you MVP's haven't resolved this. I had one
computer on my network getting the "Limited or no connectivity" message.
After researching MS Knowledge Base I tried two solutions. Repair the
TCP/IP stack and reset the WINSOCK file both using the NETSHELL utility.
Apparently either a virus or malware is corrupting these files. I could not
get an IP address from DHCP. Tried static IP address. I could then see the
network, but still not get on the internet. This led me to believe there
was a problem in the files that IE actually uses to connect. Voila, reset
WINSOCK file and it worked. The thing that makes me believe that malware or
viral infection is causing it is that I NEVER download anything unless I
know what it is. However my son's computer on the same network was consumed
with spyware and Trojan downloaders. Apparently it came across the network
and hit my computer. How do I know this is posssible? After repairing the
problem on my computer yesterday my other computer which like a dumbass I
turned off all Antivirus and Antispyware while doing video capture acquired
the same exact problem!!! I reenabled all the Anti-Stuff, ran viral and
spyware scans then reset the TCP/IP stack and the WINSOCK file. Again, Voila
it worked. Sorry to be so long winded but I think a lot of these problems
people are seeing is related to this. A friend that works on computers says
he's seeing a lot of the same issues. There are WINSOCK hijackers out
there. This should help a lot of people.
 
OK, I've seen too many references in other posts concerning similar
problems. I'm suprised some of you MVP's haven't resolved this. I had one
computer on my network getting the "Limited or no connectivity" message.
After researching MS Knowledge Base I tried two solutions. Repair the
TCP/IP stack and reset the WINSOCK file both using the NETSHELL utility.
Apparently either a virus or malware is corrupting these files. I could not
get an IP address from DHCP. Tried static IP address. I could then see the
network, but still not get on the internet. This led me to believe there
was a problem in the files that IE actually uses to connect. Voila, reset
WINSOCK file and it worked. The thing that makes me believe that malware or
viral infection is causing it is that I NEVER download anything unless I
know what it is. However my son's computer on the same network was consumed
with spyware and Trojan downloaders. Apparently it came across the network
and hit my computer. How do I know this is posssible? After repairing the
problem on my computer yesterday my other computer which like a dumbass I
turned off all Antivirus and Antispyware while doing video capture acquired
the same exact problem!!! I reenabled all the Anti-Stuff, ran viral and
spyware scans then reset the TCP/IP stack and the WINSOCK file. Again, Voila
it worked. Sorry to be so long winded but I think a lot of these problems
people are seeing is related to this. A friend that works on computers says
he's seeing a lot of the same issues. There are WINSOCK hijackers out
there. This should help a lot of people.
Click to expand...

Doug,

Lots of different software installs components into the LSP/Winsock.
- Firewalls.
- Malware (spyware, viruses).
- Port monitors.

Any software, removed improperly, will leave components behind. If the software
removed leaves components in the LSP/Winsock, you end up with a corrupted
LSP/Winsock. This results in symptoms with varying severity.

Repairing the LSP/Winsock by Netsh is used for XP SP2 systems, but not with 100%
success. For non XP SP2 systems, and for XP SP2 systems that are not
successfully repaired by Netsh, one can also try LSP-Fix
<http://www.cexx.org/lspfix.htm>, WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
<http://www.spychecker.com/program/winsockxpfix.html>.

Failing that, as you indicated, resetting TCP/IP is also know to work.

The frustrating thing is that any one of those solutions may or may not work in
any given situation. And, once a solution is found to work, you can't try
another solution, so there's no way of knowing which solution works best
overall. All you can tell is "In this case, Solution A didn't work, but
Solution B did".

Of course, as you discovered, the best solution is prevention.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.
 
Back
Top