Cant renew IP

[smartfan]

Hi !

I hope someone can help me...
I have a homenetwork with 3 computers 2 of them run Win XP with SP2
and 1 run Win 98.
Now to my problem..

One of them with XP get no IP from the router so it cant connect to the internet
It just got a 169.xxx.xxx.xxx private adress
I just lost connection a few days ago.
I have tried everything..If i put the cable in another computer it works fine
so the cables and router are no problem.
It responds on local ping 127.0.0.1 and it responds to ping on the 169.xxx.xxx.xxx adress too
DHCP is activated and Windows networkconfiguration is also OK
I have tried with 3 different Networkadapters but it makes no different..
Still got no IP from the router. But lights indicates that the adapter have contact with the router

I put in another harddrive with Win 98 installed..no connection
So yesterday i reinstall Win XP and hope it will work but NO..
Run ipconfig dont help either
I try to assign the default gateway IP manually then ping the router but still no respond...
Have i forgot to do something ?
I think this must be hardwarerelated..Can it be something wrong with the motherboard ? I also check BIOS but there is no parameter for NIC
Anyone have some ideas ?
I will be greatful for all help..Thanks

[berrybry]

Could try taking a nic out of a working computer and putting it in the one thats not working. That will tell you if its hardware. (assuming its not onboard lan) I believe ping 127.0.0.1 only checkes the software IP stack not the actual hardware but i could be wrong. Try reloading the Lan drivers.
run this command "netsh int ip reset logfile.txt" it will reset your ip stack.
(although a reinstall should have done that.)

The NIC card shows up in device manager?
Did any thing change from when you had connectivity until you lost it?
Try other ports on the router/hub/switch?

[Rainbow]

Nope your winsock file got hosed....google winsock repair and youll find the neat little program to fix this...I think its called winsock xp fix.

[BioGhost]

127.0.0.1 is the loopback address which tests that TCP/IP has been installed properly. 169.X.X.X is and IP class that windows uses to assign a TCP/IP to a NIC that cannot get one from a DHCP server.

Rainbow could be correct that your winsock file is corrupted or your hosts file has been hijacked.

You could also look to see if there are multiple winsock files which could cause a confliction.

I would try resetting the router to its factory defaults.

ANy firewalls that maybe blocking that PC?

[ace]

Originally Posted by Rainbow

Nope your winsock file got hosed....google winsock repair and youll find the neat little program to fix this...I think its called winsock xp fix.

I think this is the one he is talking about. I have use this countless times to reapir customers computers.


http://www.xp-smoker.com/freeware.html

[Rainbow]

Originally Posted by ace

I think this is the one he is talking about. I have use this countless times to reapir customers computers.


http://www.xp-smoker.com/freeware.html

Yep thats it.
Ok so my memory's not as good as it use to be whats yer point

[TonyT]

It's not a hosed winsock because he fails to obtain an ip address even after swapping drives in the comp:

I put in another harddrive with Win 98 installed..no connection
So yesterday i reinstall Win XP and hope it will work but NO..

thus he defintely has a hardware problem, most likely the cable is bad or the router port is bad. The led lights on the nic & router for that connection cvan still light up even is the cable or port itself is bad, meaning one wire in the cable or port is afoul.

solutions to try:
change cables
change the port the cable uses.

routers are known to have ports die, it's not uncommon