Computing.Net > Forums > Networking > DHCP error and 169.*** IP adress

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

DHCP error and 169.*** IP adress

Reply to Message Icon

Name: Ryan Whisner (by rwhisner41)
Date: April 16, 2007 at 15:52:25 Pacific
OS: Windows XP
CPU/Ram: Pentium 3 - 512 RAM
Product: Compaq Presario
Comment:

So I just recently took my desktop from my dad's house which was running the internet directly from the modem into the computer, and then hooked it up to my mom's wireless router while I was staying at her house.. The internet worked on all other computers in my mom's house but only worked on my computer for about 20 minutes and then shut down, while still running fine on the other 2 computers.

So tonight I took my desktop back to my house and I connected it back to the modem like it was right before I left.. All of the lights on the modem that are supposed to be on are on. My IP adress is starting with a 169.*** number with and without the cable plugin screwed into the back of the modem..

Anyone know how I can fix this? The customer support guy for my ISP told me to go into RUN prompt and type in cmd and then do the ipconfig and all that.. He then told me to try /renew or whatever it is and still no results..

Someone told me to turn the computer off and turn the modem off and then let the modem run for 5 minutes before turning on the computer. Nothing happened, no change.

Ipconfig/release and renew doesnt do anything for me either. I keep getting a 169.*** ip adress.. Anyone know how to fix this?

SOMEONE PLEASE HELP!!



Sponsored Link
Ads by Google

Response Number 1
Name: jefro
Date: April 16, 2007 at 19:05:32 Pacific
Reply:

You would need to start at the ISP that provides service. There are a few thousand ways one might connect.

The 169 tells us that the next device upstream isn't providing a dhcp response.

I read it wrong and answer it wrong too. So get off my case you goober.


0

Response Number 2
Name: heropsycho2177
Date: April 16, 2007 at 19:10:05 Pacific
Reply:

You're getting an APIPA address because your computer is not for whatever receiving a DHCP lease.

There are some troubleshooting that can be done to narrow down the problem, but try this first in the off chance your TCP/IP stack is hosed.

start - run - cmd

ipconfig /renew... Just kidding...

At the command prompt:

netsh int ip reset c:\resetlog.txt

This rebuilds your TCP/IP stack settings in Windows.

If that doesn't work, post back.

"Enough, enough bowing down to disillusion!
Hats off & applause to rogues & evolution!
The ripple effect is too good not to mention.
If you’re not affected, you’re not paying attention!"


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: DHCP error and 169.*** IP adress

internet sharing www.computing.net/answers/networking/internet-sharing/7054.html

mac/pc file sharing www.computing.net/answers/networking/macpc-file-sharing/24670.html

IP Adress conflict in wireless LAN www.computing.net/answers/networking/ip-adress-conflict-in-wireless-lan/16512.html