One computer decided to S.T.B.

[boatgod]

As usual, I'm still not smart enough to fix my problems so I come here! I have a desktop (win xp home) that decided it didn't want to see the network or connect to the internet anymore. This is pre SP 2. I have tried ipconfig tricks, (release, renew, won't renew, get some funny 169.xxx.x.x address) disconnecting the wireless, and even went so far as to go ahead and install XP2. I've ran spy bot s & d, adaware. The rest of the computers on the network have no problems. It's like this one all of a sudden decided that it won't connect to the net any more...This computer runs non-stop and seems to have developed the problem after the last download of seti@home work units. The other 3 computer on my net are xp home, SP2. My HJT doesn't show any recognizeable problems. Anyone???

[dsl boy]

try setting an ip in the local area connection properties that would be handed out by your router's dhcp. for example if it was a linksys router: 192.168.1.200.

getting that default windows ip is what is doing you wrong. most times it is from a blown tcp stack that makes it default like that. you could also try typing these in a command prompt.

netsh int ip reset resetlog.txt
netsh int ip delete arpcache

hard return after each line. should say ok after second then pc will need a restart.

hope it helps.

[glc]

http://www.spychecker.com/program/winsockxpfix.html

[dsl boy]

there is also a win xp sp2 winsock fix that makes it so you don't have to download any third party software. type into command prompt like above:

netsh winsock reset

only works with sp2. make sure you uninstall any firewalls (excluding sp2 firewall) before hand.

[boatgod]

Thank you so much. I went back to the computer after dinner and it was online again. Weird. Should I mess with those commands or just leave well enough alone?

[dsl boy]

the first set of commands could possibly help, but the second (winsock) commands should only be done as a last option.