Ipconfig fails in XP

I believe this is related to the sasser virus. I was connect to the work and recieved a message that my machine was infected. They then promptly shutdown my PC. Since then I have been unable to access the internet at all. My limited knowledge was to try and renew/release the IP info but I get the error message in this thread.

Would love to hear anyones suggestions.

google housecall?

[Jason425]

I was telling him to type housecall in google if he wanted to find it.. http://housecall.trendmicro.com/

@mobyplay2001

AN ERROR OCCURRED WHILE RENEWING INTERFACE LOCAL AREA CONNECTION: AN OPERATION WAS ATTEMPTED ON SOMETHING THAT IS NOT A SOCKET

This is usually as a result of some programs messing with your tcp/ip protocol stack an easy fix for this usually be to reset yoour tcp/ip stack easiest way do do this is to start up google(*on another pc*) search for "lsp fix" you should find a lot of programs that'll help you there. i personally prefer WINSOCKFIX from option explicit it'll get the job done the quickest plus it also come with another very handy tool

btw if you had any manually set tcp/ip settings then you'll have to do them over if u use winsockfix

well here is a variation on the same issue, what do people think?
a) when I tried to run ipconfig from the DOS prompt, I got "ipconfig is not recognized as an internal or external command, operable program or batch file"

b) when I tried to run ipconfig from the Run menu, I would get an error message telling me that ipconfig is not a recognized and that Windows could look online for the right program or I could select from a list

Well, I fixed a) by going to Computer -> Properties -> Advanced -> Environment variables and replacing the PATH command (that somehow had been repplaced leading a folder for my Treo?) with C:\Windows;C:\Windows\System32, my ipconfig/all at the DOS prompt works, thought it still doesn't from the RUN menu.

now that a) has been addressed, do people have any thoughts about b)?

I've been having similar problems.
Tried the netsh to reset TCP/IP ... no luck.

Came upon some other information that looks promising. Other forums have reports of, with XP, recent TCP/IP and WINSOCK stack corruption. This appears to either be caused by spyware or simply the fact that since TCP/IP is now deemed a critical 'core' networking component of XP, its a little more fragile than in previous Win O/S versions.

Following are a couple of tools to try ... one to repair the TCP/IP stack, the other for WINSOCK. I have not tried these yet ... but I intend too soon. These tools have apparently aided others in getting this %$&@ problem solved.

TCP/IP - http://www.cexx.org/lspfix.htm
WINSOCK - http://tntmax.com/Download/Software/WinsockXPFix.exe

Best of luck.

I had this issue doing an inplace upgrade from W2K to XP.

My Resolution:
I uninstalled TCPI/IP protocol, Client for MS networks, and F&P sharing service from the NIC. Rebooted. Go back to Network connections, you should have no services, clients or protocols installed (or "bound" to the adapter). Click install to reinstall the necessary protocol, client and services. Add TCP/IP, Client for MS networks, and F&P sharing service. Immediately after doing this my NIC was active and it received a DHCP assigned IP address. Problem solved.

Originally Posted by matt1968

Ipconfig says internal error, request not supported, unable to query routing information.

I already reset tcp/ip with netsh

Thanks for any ideas!

HI, Did you ever get this resolved? (wireless card)
Had you upgraded the router firmware or driver before this happened?
That's what happen to me! and then it blew out my LAN net connection. I had to roll it back 3 days because MS and Dlink couldnt fix it. Every time I reinsert the wireless card, it happens again! Time to find the magic combo of firmware and drivers ;( or maybe take a trip to Costco and get a Diff make setup.

NO virus detected!

1st want to thank the many posts that help lead me to full success. It was a combo of events listed below. Needed all steps. Good news is I did NOT need to reinstall XP or use WINSOCKFIX utility.

System
Win XP Home Edition.
Home Wireless Network 801.11b
Installed Adware6 to attempt to eradicate Spyware
Norton AntiVirus Installed
Peer to Peer Network. Using One PC as "server" which connects directly internet and provides access to internet for client PC's (ie. not access point or router)

Symptoms. XP Client PC's on Wireless Network running very slow. Finally will no longer connect to wireless network. IP address on my "server" PC is 192. ... but IP address on clients is 169. .... Can't ping server. However, I knew WI-FI hardware is working because still have WI-FI connectivity to client PC's on network running Win98SE.


Steps

Virus Check

1. Run Norton AntiVirus - No viruses found

Adware/Spyware Eradication

2. Start->Control Panel>Remove Software. Viewed all programs and using Google Search as a reference removed all programs that were spyware/adware
3. Used Tasked Manager (cntrl-alt-del) and MSCONFIG (using Start-Run-CMD line) to view startup and process see all adware/spyware. Again used google to discern which programs/processes were adware/spyware.

4. Adware Spyware still running included TV Media and Winupdtr. Deselected these programs from MSCONFIG startup. Deleted files in C:\program Files\ and deleted keys from registry using regedit per postings above... but did not permanently eradicate TV Media

5. Manually removed TV Media registry keys using instructions at www.kephyr.com and/or posting above. But also must immediately do step 6 below.

6. Utilized posting that said TV Media was linked with Explorer. Must "Kill" Explorer Process in task manager, Killed Explorer, then used cntl-alt-delete to bring up Task Mgr again. Start CMD line from Task Manager and used CMD line to navigate to c:\Program Files\TV media files. And then delete using delete c:\Program Files\TV Media\*.*

Note to reboot I had to specify which mode to restart in while in MSConfig window. (For some reason my PC would not startup in SAFE mode by tapping F8 during reboot.) 1st selected Diagnostic Startup mode. (Could also go to WIN.BOOT tab to start in SAFE mode.

7. Used MS article "How to Determine and recover from Winsock2 corruption" found at support.microsoft.com/?kbid=811259 (I did have some corruption).

8. Opened Network Connections window. Right mouse click on Wireless Connections to open properties. Uninstalled Client for Windows, File and Printer Sharing, and deselected TCP/IP items. (Note: there is a posting to manually deinstall TCP/IP. I didn't do it).

9. Reboot.

10. Opened Network Connections. Right mouse click on Wireless Connections to open properties. Install Client for Windows, File and Printer Sharing, and TCP/IP items. Select Wireless tab. Selected Properites and Advanced tab for preferred network and ensure all settings were correct in accordance with postings above (I use WEP enabled)

11. Rerun "Setup a Home or Small Office Network" on client

Still had 169... IP address on client PC. The final solution not found above was Drumroll please......

12. Rerun "Setup a Home or Small Office Network" on my Server PC. IP address on Server changed from 192.68.0.1 to 192.168.0.1 and full connectivity was restore between all PC's on network and with the adware gone PC's are fast.