IP Address hlp.

[²JPortv2²]

Hi,

My friends desktop computer is connected to a linksys router. it was working fine but now the desktop cannot access the internet. So i checked the ip address and i found it was the wrong ip address. it started with a 169 when the routers address is a 192. so i tried to release and renew the ip address but when i tried the release ipconfig/release the system just shows me the ipaddress and it dosen't release the ip. i tried the renew anyway ipconfig/renew and same thing happens. So i bought the system home and connected it directly to my dsl modem. i did ipconfig and it shows the same ip address that it showed at my friends house. the 169. and even though i was connected directly to the modem i still couldn't access the internet. Oh its Win XP Pro Ed. I was just going to remove it boot then replace the NIC but i found it was an onboard NIC. So the next thing i tried was i uninstalled the drivers for the NIC and then reinstalled them. This didn't work either. Same ip the 169. Please help me to fix this problem.

 

[Yakbak]

Do the lights on the network card and router port show a connection to the computer? If so, then try setting your network card to Auto-Negotiation for speed and duplex.

If that still doesn't work, try pinging your localhost IP, then the router IP to see if you can see it.

You can also try giving the computer a static IP in the same mask as the router.

 

[²JPortv2²]

ok i'll give it a try.. Thanks

 

[jajmon]

Do the lights on the network card and router port show a connection to the computer? If so, then try setting your network card to Auto-Negotiation for speed and duplex.

If that still doesn't work, try pinging your localhost IP, then the router IP to see if you can see it.

You can also try giving the computer a static IP in the same mask as the router.

The router is on a different network than his pc, 192 vs 169, so pinging the router without a gateway to 192, won't work - forget that

> the nic went bad
> the port on the router went bad
> the IP stack is hosed
> the cable went bad

Try a different port on the router - no work, then,,,,
> try another cable - no work,,,,
> delete the IP protocol | reboot | add IP | reboot ,,,, no work
> try another nic - disable the onboard nic

last resort = format

 

[FunkDaMonkMan]

I had the same problem (see my thread below). No answers... so i am reformating. I'll let you know how it goes.

 

[Yakbak]

The 169. address is a self assigned private IP that occurs when there is no DHCP IP obtained. Most likely the computer cannot see the router and pull its internal IP from it via DHCP, so I would check the connectivity between the computer itself and another computer, or check the network card settings or even the physical cable itself.

 

[andy334]

I had the same problem and winstockfix did the job