Static IP keep dis-appearing

the computer won't hold the static I put in. It keep reset to Automatic Assigned mode.

Does any one know what cause this?

 

Welcome to the forum.

I know you are running XP because I moved the topic from that section but home or pro version and what SP? Also, what sort of network connection?

 

sorry,

Windows XP Pro with SP2.
The computer has both Wired and Wireless NIC. This particular computer use only Wireless NIC which is an USB Wireless NIC made by LinkSys. I noticed that this problem started to occur after I cleaned the spywares on this computer. The network setup is very basic. Cable modem > Wireless Router > computer. This network only have 1 computer.

The IP and subnet I use for this is.
IP: 192.168.1.2
SN: 255.255.255.0
GW: 192.168.1.1

 

That helps. At a guess, the problem is most likely a spyware damage leftover. Try the following. It will reset TCP/IP back to the defaults and you'll have to set up networking again but the problem may go away. If not, we can dig around some for another cause.

start->run->cmd and OK to open a cmd window
netsh int ip reset C:\resetlog.txt and ENTER

 

There are also some fixes for XP Winsock and LSP, described in this link. I've fixed machines with these problems by hand. They seem to have some utilities now that supposedly automate this. I haven't tried them myself.

If you follow the Microsoft instructions make sure you know where those INF files are. I didn't always find them in C:\Windows\inf. I believe they are supposed to also be on your installation CD.

http://www.cit.cornell.edu/computer/security/spyware/repair.html

 

Hi aspicer and welcome. Hope you are staying dry and hope the nasty that is trying to brew up in the Caribbean can't manage to organize. We've pretty much had enough weather for this year.

The fixes you mention usually match up with problems that prevent connections (socket damage from spyware and suchlike).

Certainly possible that the same critters could cause this but usually the internal confusion within TCP/IP is more the sort of thing you'd want to fix by removing TCP/IP and reinstalling it if XP permitted that as earlier OS versions did.

If the netsh reset fails, a winsock fix is certainly the next thing to try along with some spyware cleanup in case SamayouSamurai has problems he hasn't noticed.

 

* I think you are right. So they should try the ip reset first. Personally I've never seen that to fix anything. But that could be just my personal experience. I've seen some weird stuff spit out of Windows after spyware has been into a machine, like weird ascii characters from a simple ping. That Winsock fix has been a miracle cure for about the last 4 or 5 spyware botched machines I've worked on. Although I also usually try netsh ip reset first myself.

Thanks for the welcome. I often run into some pretty well botched up an not updated laptops on motor yachts here. Many only have 64K Internet via Satellite and occassional in dock WiFi. They often don't have the bandwidth underway to download fixes or updates.

You're right we don't need any more storms around here AT ALL!

 

I know the IP will stay for a while and I can brows Internet, download files and use AIM etc(acording to the user). I have asked the user to run the command you mentioned to see if this IP setting reset problem would stop. Will let you know if this would fix it.

 

Well good luck with that...

Ummm, how could you have a "user" on a network that only has one computer? Oh you must be helping someone else with a 1 computer network. Or am I reading that wrong. (or am I nit picking? ;-)


Have a Nice Network -- er, um, I mean Day!

 

yup, it's the only way to bring Internet to where the computer locates without re-run coax or network cable inside the wall.

Any way, re-install of TCP/IP and SocketFix didn't fix the problem. I'll try to use repair feature from Windows XP disc to see if it can be fix.