router assigning 169 instead of 192; connection won't work

[dredd2929]

Every once in a while, my wife's laptop will connect with an IP address starting with 169.xxx.xxx.xxx instead of the usual 192.168.0.xxx. When this happens, her network connection doesn't work. Weird thing is, when I go into the router GUI, it shows an IP address of 192.168.0.xxx assigned to her laptop...completely different that what her computer shows. Releasing/renewing doesn't help. So far I've been able to temporarily fix it by just changes channels, but after 1-2 weeks the problem returns. I have firmware v1.9. Her laptop is a Dell Inspiron 6000 running Windows XP Pro. Any idea what's going on and how to fix it?

 

[theevilsharpie]

If your wife's laptop is getting a 169.254.xxx.xxx address, it failed to receive an IP from your router's DHCP server and Windows XP's IP autoconfiguration service supplied one instead. This can be caused by network communications failure (e.g. interference on your channel) or a failure of the DHCP server on the router. I suspect the latter.

 

[RebateMonger]

Strange behavior. Have you tried re-flashing the router's firmware?

Otherwise, it may be time for a new router. Or a new WiFi adapter for the laptop.

What's the length of DHCP lease that the router is handing out?

 

[dredd2929]

The lease time is 1440 minutes. It is a D-Link DGL-4300 with the latest firmware (v1.9). I noticed under DHCP Server Settings that "NetBIOS Advertisement" is unchecked. Should I select it?

 

[RebateMonger]

The lease time is 1440 minutes.

That's one day. It means that your client PCs will try to renew their DHCP-obtained IP address after half a day. And the IP address will expire after one day. You can look in your client System Event log to see if the PC is having problems renewing its IP address.

Increasing the IP address lease time to a week or a month may help things, although there's still a question of why your PC isn't getting the renewal.

What OS is your wife's laptop using? How about the other PCs?

 

[Emulex]

best to use static lease - but i've seen issues with some devices and some routes. have to get rid of one or the other poor implementation

 

[dredd2929]

Her laptop is Windows XP Pro SP3, same with the other PC.

Do I set up a static IP from the router or from the laptop? I think I remember how to do it through TCP/IP settings in the control panel, but I'm curious if there's a better way. I noticed I can "reserve" the IP assignment through the router...is that the same as setting up a static lease?

 

[JackMDS]

Static IP is set in the computer's TCP/IP.

If you use it set it to an address that is Not within the range of the Router's DHCP.

IP assignment through the Router using the Reserve feature, means that the Router's DHCP would assign to the specific computer the same IP number (it is done with the aid of the MAC address).

I.e., from the computer point of view the IP address is Dynamic and leased, but it end up always the same IP number.

you can try both methods and see which works better.

 

[AVAFREAK182]

Is her work place or something set to 169.XX.X.X?

If thats the case that is your problem.

I'm not sure if your house is DHCP (I assume it is), but I believe you will have to go in and manually change from your static to DHCP each time (I could very likely be wrong, there might be an easier way).

 

[JackMDS]

Is her work place or something set to 169.XX.X.X?

If thats the case that is your problem.

169.xxx.xxx.xxxs is Windows Default IP that is assigned if the computer's TCP/IP is set to Auto Obtain an IP, and it can Not find a DHCP IP.

I.e., it is a No IP, IP.

 

[Emulex]

i don't think i've ever seen anyone use 169 - that is where hardware goes when dhcp fails or freaky hp procurve stuff by default. I guess you can use it.

the reason i like using a static ip that is not the same as the routers default subnet is because i've seen a linksys or two reset to their factory settings - all dhcp entities would remap to the new open wifi and you could get pwned quick.

if you have static assignments those devices would be unreachable and you'd probably notice something wrong real quick.

 

[JackMDS]

Is her work place or something set to 169.XX.X.X?

If thats the case that is your problem.

169.xxx.xxx.xxxs is Windows Default IP that is assigned if the computer's TCP/IP is set to Auto Obtain an IP, and it can Not find a DHCP IP.

I.e., it is a No IP, IP.:sneaky:

 

[RebateMonger]

If you have two computers and don't provide static or DHCP addresses to them, they'll pick their own random 169.xxx.xxx.xxx addresses. These will be on the same subnet and you CAN use them on a network, assuming ALL of your PCs use the same IP selection method.

APIPA - How to use automatic TCP/IP addressing without a DHCP server:
http://support.microsoft.com/kb/220874