Sounds like you both are getting closer to a resolution on the issue with Limited or No Connectivity. I've thrown out a lot of advanced information so give yourself a pat on the back for getting this far. I'll address both your posts by heading them with your username so you know what you will want to try. The advice may apply to you both and you may want to try the advice to see if it doesn't resolve your issue for you.
I can think of two things you might try. To address your question, if you feel that Spybot erased some pertinent files which are affecting your Network Connections, you might try a System Restore. Spybot usually sets a System Restore point prior to making any registry changes in case you need to backtrack. You might check to see if there are any System Restore points which coincide with the timeline when the connectivity problems began. Check your Event Viewer if you are unsure of the exact date when the problems began. You can get there through the Computer Management console. I'd pay attention to the items in the System Log that appear to reference network connections, TCP/IP, DNS, DHCP, or your NIC hardware.
This next advice pertains exactly to your question; this is dependent on you having your Windows XP CD-ROM available. If you don't want to go through the trouble of a System Restore, you can attempt to repair the Windows system files using the System File Checker and Windows File Protection utilities. They run in conjunction and are invoked through the command line. You must first insert your Windows XP CD-ROM into the drive, if it goes into the AutoPlay routine, just cancel out. The System File Checker will need the disc there because it checks for crucial system files and will repair / replace any that have become corrupt, missing, or otherwise altered with clean ones from the /i386 folder of the disc. Invoke the System File Checker as instructed below, the link gives more information from Microsoft's TechNet site regarding use and purpose of the tool - it takes roughly 25-45 minutes to run depending on processor speed, CD-ROM drive RPM, and state of your hard drive.
Start >> Run >> type cmd.exe >> press [Enter] >> type sfc /scannow >> press [Enter]http://technet.microsoft.com/en-us/library...57126.aspx#ECAA
Now that you've gotten past the Limited or No Connectivity stage, try running the nslookup command from the command line. This will display the current DNS server that is being used to resolve URLs to IP addresses on the Internet. What we want to figure out is if you may have a conflict with your DNS server somewhere along the lines when you attempt to send a request for resolution of an HTTP page. You will need to recall [a] what your manual / static IP address was; and [b] what your manual / static DNS
Do the following:
Start >> Run >> type cmd >> press [Enter] >> type nslookup xxx.xxx.xxx.xxx >> press [Enter]
xxx.xxx.xxx.xxx is your static IP address [a].
What you want to compare is the server address that is returned from the command. It should be matching your static DNS server address [b] which you entered into the Internet Protocol (TCP/IP) Properties applet when you manually configured your IP address information. If the information matches, i would suggest trying to flush the DNS resolver cache again as posted in previous posts of the this thread.
If it does NOT match, that definitely signifies a problem.
I would try looking into your HOSTS file which is located at C:\windows\system32\drivers\etc\hosts. This information is in .txt format and can be opened / edited with Notepad | Wordpad. By default the HOSTS file should only one entry, 127.0.0.1 which points to the localhost - that is the loopback address simply points ping packets to your local machine when you do the ping command. The HOSTS file is loaded into memory at startup to aid in DNS resolution for URL to IP address; you can alter this file yourself with static IP address information for known URLs; your machine will parse this file before contacting a DNS server if the URL you are visiting is listed and can help guarantee that your browser will not be redirected to a spyware infected site.
If you notice that your HOSTS file has a bunch of other entries for other webpages and sites, you may have spyware problems or your browser may have been hijacked which will possibly require a reinstallation or System Restore.
NOTE: by default Spybot S&D will plug in entries for known spyware / malware sites to point back to the local machine. They will be prefixed with a comment indicating that the entries were added as part of Spybot to redirect known spyware / malware sites back to your local machine as a preventative measure to avoid sending your browser to a hijacked webpage. By default, the HOSTS
See what you guys are able to find out and post back.
Edited by Cyb3r_Ninj@, 03 January 2008 - 02:30 PM.