TCP?IP traffic failure?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I recently took an idled winxp sp2 machine (desktop) that is (was) hooked up
to the home network via wireless and added all new updates successfully,
restarted, and all was OK. then added Microsoft Antispyware, and rebooted
successfully, then removed several adware apps found by MS Antipyware, w/
MSAntispyware, then was requested to reboot ....

Since that last reboot, the wireless zero-config sees a strong signal from
the AP, apparantly connects, but shows "Limited or No Connectivity" and a
DHCP address request failed (ip config shows that no address was obtained)

My other notebook connects to the same AP fine. I've turned off
MSAntispyware, turned off Windows Personal Firewall, there is no port
filtering in place, BUT it just seems as though something is "blocking" all
TCP/IP traffic. I've disabled/reenabled the wireless connection many times.
I've unistalled the wireless hardware then reinstalled, all to no avail.

Even the utility provided by the wireless adapter fails to obtain an address
from the DHCP server in the AP. AND, manually assigning IP, subnet, DNS, etc
fails to provide IP connectivity to the wireless AP. ... I'm stumped. I find
it hard to believe the hardware "failed" at the same time MSAntipsyware was
installed and used to remove adware ...
I'm going to next try to uninstall MSAntipyware. I don't have a recent
restore point to go back to. And see what happens.
How can one "uninstall" all networking components, then re-install them?
How can one determine if there is "something unknown" blocking TCP/IP traffic?

Thanks in advance.
 
I recently took an idled winxp sp2 machine (desktop) that is (was) hooked up
to the home network via wireless and added all new updates successfully,
restarted, and all was OK. then added Microsoft Antispyware, and rebooted
successfully, then removed several adware apps found by MS Antipyware, w/
MSAntispyware, then was requested to reboot ....

Since that last reboot, the wireless zero-config sees a strong signal from
the AP, apparantly connects, but shows "Limited or No Connectivity" and a
DHCP address request failed (ip config shows that no address was obtained)

My other notebook connects to the same AP fine. I've turned off
MSAntispyware, turned off Windows Personal Firewall, there is no port
filtering in place, BUT it just seems as though something is "blocking" all
TCP/IP traffic. I've disabled/reenabled the wireless connection many times.
I've unistalled the wireless hardware then reinstalled, all to no avail.

Even the utility provided by the wireless adapter fails to obtain an address
from the DHCP server in the AP. AND, manually assigning IP, subnet, DNS, etc
fails to provide IP connectivity to the wireless AP. ... I'm stumped. I find
it hard to believe the hardware "failed" at the same time MSAntipsyware was
installed and used to remove adware ...
I'm going to next try to uninstall MSAntipyware. I don't have a recent
restore point to go back to. And see what happens.
How can one "uninstall" all networking components, then re-install them?
How can one determine if there is "something unknown" blocking TCP/IP traffic?

Thanks in advance.

What you're describing sounds like LSP / Winsock / TCP/IP corruption, which is
frequently seen after removal of malware. My article will explain how to
proceed:
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top