• 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=DHCP Problems?

B

Bob Johnson

n00b
Joined
Aug 7, 2004
Messages
41
I am having a problem pulling an IP for my network. Everything was working fine until a few days ago when I suddenly lost my connection and connected to a 169 address. I know that this is an IP in windows when you can't pull an IP from the network. When this happened I released/renewed my IP and that worked for about a half hour then I reverted back to the 169. I've tried everything I can think of, including drivers, cables, and system restore. My last option seems to be reformatting but I'm reluctant to do that. Is there anything that I have missed?
 
How big is the network? Where do you pull DHCP from? A server, DSL/Cable router, what?
 
The 169 address is what windows automatically assigns when it tries to get an address from a dhcp server, and is either unable to find a server, or is denied an IP address by the server it can find (eg. MAC address filtering)
 
Its the network at my college. I've called the support people, but they couldn't help me since the problem wasn't with my access point, it was with my own computer.
 
Sounds like crappy support to me.

It's not impossible that your access point isn't the problem...
 
Real quick... is this a wireless connection? If so, and assuming you have/can get the wireless utility that comes with all pcmcia/pci wireless cards, I'd uninstall the card (built in or no), disable microsoft's auto-wireless-config, and re-install the card using it's own wireless config program.

If it is built in, just try uninstalling/re-installing the card.
 
Nah, its a wired LAN. I know that it's my computer because I tested my laptop on the same access point and i was able to get a connection via wired.
 
Bob Johnson said:
Nah, its a wired LAN. I know that it's my computer because I tested my laptop on the same access point and i was able to get a connection via wired.
Click to expand...

In that case, I'd say it sounds like hardware, be it the cable you're using, or the nic itself. Do you have a spare PCI NIC laying around?
 
Try changing what the mac address is on your desktop, to what it is on your laptop's NIC (You can do this several ways, try googling it for more details)
 
Having multiple network adapters enabled can cause this problem. Look under Network adapters in Device Manager.If you see multiple NICs or a Firewire controller and you don't use firewire, disable (do not delete or uninstall) the extra adapters and see if it corrects your problem.
 
Nah, its not a hardware problem, and I already checked the cables and windows says that my NIC is still good....is it possible that I got virused in some way?
 
Do you get a connected or 'limited connectivity error" with the connection? Its possible the wire itself is the issue, unless you can plug in a different machine and it works fine?
 
Maybe something fouled up with the ARP cache?

Open the command promt and type:
netsh interface ip delete arpcache

Then try a /release and /renew

Also check your System Event log, sometimes errors will get logged there. Looking for any red-errors, especially any that talk about DHCP, IP address, or anything similar to that.

It could be that the DHCP server is assigning an IP address and the client is rejecting it because the client thinks that it is in use already.
 
sounds like a corrupt ip stack

win 2k? Uninstall/Reinstall the TCP/IP Protocol
win xp? start > run > cmd > "netsh int ip reset log.txt"
 
I tried resetting the IP stack and it just hung there, so I assumed that it was a virus that had completly corrupted my stack, so I reformatted but it still doesn't work, but there's a new problem: I can't release my IP address now. Are there any physical ways of testing an integrated NIC for damage? Also, would I even be getting a 169 IP if my NIC was broken?
 
You must log in or register to reply here.
Back
Top