I'm working on an HP notebook computer running Vista Home Premium x64. The computer appears to have been infected with some kind of malware which I removed, however neither wired nor wireless networking is working. This computer uses an Intel wifi Link 5100 AGN adapter and a Marvel Yukon 88E8040 adapter. In the case of the wireless adapter, the problem appears to be that I can attach to the wireless network and I'm able to set the network to "Private" and according to "IPConfig /all" the adapter is able to get an ip address; default gateway; dns; etc but all attempts to ping the router return "Request timed out" but I am able to ping 127.0.0.1 the local host and get a response. So far I've tried these assorted things to correct the problem, without success: Windows Firewall is off ran netsh winsock reset ran netsh int ip reset ran sfc /scannow updated to the latest drivers from Intel & Marvel device manager indicates "This Device is working properly" for both Nothing I've done seems to make any difference in the nature of the problem. Also while the user only connects via wireless, the wired port appears to be non functional since when I attach a wire to my test router I'm not getting a link or activity on the router (and I've tried three different cables), the port on the computer does not have status lights. Can anyone make a suggestion here on what may be preventing the tcp from passing data? - Norm

Hi Sabrina: They use some anti-virus by WebRoot. This computer belongs to a friends wife and this network problem existed at their house first and other wireless computers were able to access the internet while this one was not. Also while I've been working on it at my house other computers and wireless devices are able to access the internet through my router so I believe that this shows without a doubt that this is not any type of router equipment problem. Previously, safe mode with networking either had the same effect (could get an ip but would not pass data) or half the time it was not able to get an address and would simply be 169.x.x.x. The suggestion of a clean boot was a good one, after disabling all startup items and non-Microsoft services and restarting the computer I was then able to ping the router. I opened a web browser and sure enough I was able to get online. I believe that at some point I had used msconfig to disable startup items but not services so I'll have to work on figuring out which service is causing tcp to fail to pass data. Thanks, - Norm