• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

169 IP Address?

L

Laky

n00b
Joined
Oct 7, 2006
Messages
27
Two days ago my internet stopped working (one wired desktop and two wireless laptops all couldn't connect), which is fairly uncommon here. At first I thought Comcast might just be down so I waited a day, then I called them up. After going through the whole "Unplug this and that", they told me to release and reset my IP, since they couldnt figure out what was wrong. After doing that it said my IP was 169.x.x.x, and they basically couldnt help me anymore.

So I googled it and I tried doing some things that people said would fix it, http://www.click2web.com/169.php -I've basically tried everything on that site, no success.

Anything that you guys think could be the problem?

I have a linksys router and a Motorola surfboard cable modem BTW.

Thanks!
 
Your router isn't handing out IPs, so windows picks a 169.254.x.x ip and hands it to you. At this point, do a reset on your router, I've found this condition happens to linksys routers when they overheat. Once you've factory reset it, go and reconfigure your settings. If this does not fix the problem, reflash the latest firmware on the router and then reconfigure your settings. Had to do that twice with my Wireless N one, pain in the ass.
 
Seems as if the DHCP on your router has stopped working properly. Check the settings to make sure DHCP is enabled, and if it isn't, enable it. However it is enabled, and still not working, open up Notepad or something of the like and copy down your current settings on the router, and then do a Reset To Factory Settings, and begin restoring settings to see if that works.

Edit: Seems as if ND40oz has beat me to the punch.
 
The 169.254.x.x address is one that Windows gives when it's unable to pick an IP up through DHCP - the whole /release, /renew process.

All that essentially means is that you're unable to establish a connection with your DHCP server, which in this case - is your router.

I would double check to ensure that DHCP is enabled on the router, but likely that isn't the case. My next step would be to plug directly into the cable modem - however, I'm not sure if Comcast has any sort of MAC address limitations. Reset the modem, then connect the computer directly & see if you're able to ipconfig /renew.
 
I'm pretty sure the router is fine, since when I had the router connected it was displaying a normal IP, but no internet connection. When I when straight from my modem to the back of the computer, that is when it started giving me the 169 IP. Also, when I have my router hooked up to my computer, I can still share files over the network, just no internet.

Do you think its my mobo's ethernet port? Would it solve it if i bought a PCI one?
 
Laky said:
Do you think its my mobo's ethernet port? Would it solve it if i bought a PCI one?
Click to expand...

Not if you can still get any sort of connectivity when you're connected to the router.

When you connected directly to the modem, did you reset the modem beforehand? I know that a lot of providers set their modems to retain the MAC address and only give out IPs to that one MAC. Reseting the modem clears this out.
 
Sounds like the breakdown is between the router and the cable modem/your pc. When the cable modems hooked up, is it getting a good IP from comcast or is it getting a 169.254 address. This is under one of the tabs on the linksys config page, don't have one infront of me, but it should say something about internet connection.

Usually to fix this, you power cycle the modem and then the router. If that is not working and you can't pull a good IP when your computer is directly connected to the modem, then the modem is hosed. Time to get a new one from comcast. Usually, instead of calling, I just walk it down to the nearest comcast place and switch it out, same when I'm having problems with my cable box. If switching out the modem doesn't fix your problem, time to get the wiring looked at.
 
Your router's DHCP functionality is not working correctly. This doesn't mean your router is broken -- it just isn't handing out IP addresses.

By the way, you can still do file sharing and other LAN transactions with a 169.254.x.x (APIPA) address -- as long as the other computers are on that subnet there souldn't be a problem with local networking.
 
You must log in or register to reply here.
Back
Top