Right so, yesterday morning I woke up and realized that I had left my laptop running so when I go to shut it down I noticed that XoftSpySE had been running and found about 183 things of spyware on my pc so I remove them and reboot my pc. When I logged back onto my pc my Local Area Connection had a little warning sign next to it saying that I had "Limited or no connectivity" on it. So I attempt to use windows built in repair system and it does not work. I check the detials of the connection and this is what is there: Physical Address: 00-C0-9F-AB-F1-3F IP Address: 169.254.203.57 Subnet Mask: 255.255.0.0 Default Gateway: DNS Server: WINS Server: Now I don't know much about networking but I am sure that Default Gateway, DNS Server and WINS Server should have some values right? So I pop in the windows disc and just repair my copy of windows and it still did not fix it, I have even tried various types of programs to reset the TCP/IP settings back to the defaults. Here are my specs... Model: Hewlett-Packard zd8000 (Laptop) CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz Memory: 510MB RAM OS: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519) NIC: Realtek RTL8139/810x Family Fast Ethernet NIC #2 I have also tried switching cables and ports around to see if it is a burnt out port and it appears it is not. Also the network is working with all my other computers as well, I am pretty sure that the spyware removed something. Oh and my ip is assigned using DHCP, I also cannot access the router by its ip address (192.168.0.1). Any suggestions?
Sounds like the spyware installed a nasty little loopback proxy, which when removed, left a hole in your network stack. In other words, "Windows is broken, reinstall". :x:
I've solved the issue, I manually re-configured my TCPIP stack using settings from another computer on the network... everything is alright now
Wooo, you're lucky. I just had a friend who had his TCP-stack hijacked recently. In that case there's no elegant way to fix it. Probably this spyware only redirected you through an outside proxy, or changed your DNS settings.