Solved w32/nuwar.sys virus

I copied the tcpip.sys file located in C:\WINDOWS\$hf_mig$\KB917953\SP2QFE to the C:\WINDOWS\system32\drivers folder then rebooted...but don't have an internet connection... so I couldn't do the online scan with Kaspersky WebScanner

 

Are you trying to connect wireless or wired? Have you tried both?

 

Open the tcp.bat file by right clicking and selecting edit. Replace it's contents with the contents of the quote box below then close saving the changes.

Double click tcp.bat to run and post the contents of tmcom.txt

 

I have tried both and still no access.

 

Open Network Connections and right click>Properties of the connection. Select Internet Protocol (TCP/IP) and click Properties. Verify that both IP Address and DNS Server Address are set to be obtained automatically. Select the same on the Alternate Configuration tab. OK your way out.

Run WinsockFix again then reboot.

 

This appears to have been created just last night ......... C:\Program Files\ACW
What is it?

 

I checked the network connection properties...they seem set ok.
I tried the winsock again, but no change.

 

Since it's empty, delete the ACW folder. Try the following commands as well.

regsvr32 Shell32.dll
regsvr32 Oleaut32.dll
regsvr32 Actxprxy.dll


A reboot is required for changes to be effective.

 

ok, that's done.
But, no change after the reboot.

 

Go to Start > Run, type cmd and hit enter.

At the command prompt, type:

netsh int ip reset c:\resetlog.txt

Reboot.

If still not working, open a command window again and type the following then hit enter.

ipconfig /all >> c:\config.txt

Post the contents of both C:\resetlog.txt and C:\config.txt

 

ok,
the results of the reset log was:
<completed>

the results of the config was:

Windows IP Configuration

An internal error occurred: The request is not supported.


Please contact Microsoft Product Support Services for further help.



Additional information: Unable to query host name.

 

Go back to the Network Connections Proerties page of the connection, select and remove each of the following.

Internet Protocol (TCP/IP)
Client for Microsoft Networks
File and printer sharing for Microsoft Networks

Close and reboot.
Go back to network connections and add the protocol, client and service. If still no connection, reboot again.
If still nothing, try running the ipconfig command again.

 

You may not be able to uninstall the Internet protocol ....... just uncheck it and recheck after reboot.

 

ok,
did those things, but no luck.
the new config still has the same internal error as before

 

See if the file nettcpip.inf is present on the computer, likely in the C:\Windows\Inf folder (the Inf folder is a hidden folder). If present, open the connection properties and click Install>select Protocol>click Add>select TCP/IP then click Have Disk. Browse to and select the nettcpip.inf file and click OK. Reboot

Do you have an XP cd?

 

tried that, rebooted, still no access.
I don't have an XP cd because it came with pc...but i can try to find one, if you think reloading everything would help

 

I was actually just wanting you to try running sfc (System File Checker), which generally prompts for the cd if a problem is found.

Try this command from a command window now.

netdiag /test:winsock /v

You can copy the results by clicking the little dos icon in the top left corner and select Edit>Mark, then drag the results to highlight, then click Edit>copy. Paste to notepad and save.

Verify please that the tcpip.sys file is still present in the C:\Windows\system32\drivers folder.

 

I tried that command,
but I keep getting " netdiag is not recognized as an internal or external command. "

as far as the tcpip.sys,
in the folder there is only tcpip6.sys.

 

Try again to copy tcpip.sys from C:\WINDOWS\$hf_mig$\KB917953\SP2QFE to C:\Windows\system32\drivers

Once you've verified that it is indeed in the drivers folder, reboot. Verify that it is still in the drivers folder.

 

Dave,
YOU ARE AWSOME!
when I added the tcpip.sys this time into the driver folder, everything seem fixed. My log on was much faster and voila...I have access to the net!