169.254.x.y ?

[GWB]

I have a DSL network with a Linksys A+G wireless router. Several wired
computers, 3 fixed IP address printers and a fixed IP address shared
storage. In addition, up to 4 wireless connections.

Periodically, maybe once to three times a week, I have wierd connection
problems, usually starting with someone not being able to print. Both wired
and wireless.

After analysis, I find that some, not always all, of the DHCP connected
computers have an IP address of 169.254.x.10y and a mask of 255.255.0.0 but
since the printers are all static in the subnet of 192.168.1.10X none of
the rogue ip addressed computers can see the printers.

After two days of unhelp from Linksys, the technician told me that when the
DHCP server quits, Windows defaults to this subnet and thats where the
addresses are coming from.

Is this true? and if so, is there some way I can configure this to simply
quit if the address no longer is correct? This is really a giant PITA
because of the mix of addresses. Once the router is power reset, it
functions OK but leaves all these odd ball addresses out there. I cannot
get them to /RELEASE or /RENEW reliably and must power everything down, then
power the router back up, then all the computers as the only predictable way
to get the correct addresses back.

I am still jacking with Linksys to get them to replace the WRT55AG router,
in the meantime I put on a spare WRT54 router on the network and it is
working fine.


Is the 169.254.x.y story really true?

Has anyone experienced this and is there a recommended workaround?

TIA, GWB

 

[Pegasus \(MVP\)]

I have a DSL network with a Linksys A+G wireless router. Several wired
computers, 3 fixed IP address printers and a fixed IP address shared
storage. In addition, up to 4 wireless connections.

Periodically, maybe once to three times a week, I have wierd connection
problems, usually starting with someone not being able to print. Both wired
and wireless.

After analysis, I find that some, not always all, of the DHCP connected
computers have an IP address of 169.254.x.10y and a mask of 255.255.0.0 but
since the printers are all static in the subnet of 192.168.1.10X none of
the rogue ip addressed computers can see the printers.

After two days of unhelp from Linksys, the technician told me that when the
DHCP server quits, Windows defaults to this subnet and thats where the
addresses are coming from.

Is this true? and if so, is there some way I can configure this to simply
quit if the address no longer is correct? This is really a giant PITA
because of the mix of addresses. Once the router is power reset, it
functions OK but leaves all these odd ball addresses out there. I cannot
get them to /RELEASE or /RENEW reliably and must power everything down, then
power the router back up, then all the computers as the only predictable way
to get the correct addresses back.

I am still jacking with Linksys to get them to replace the WRT55AG router,
in the meantime I put on a spare WRT54 router on the network and it is
working fine.


Is the 169.254.x.y story really true?

Has anyone experienced this and is there a recommended workaround?

TIA, GWB

The technician is correct: If the PCs are unable to obtain an address
from your DHCP server then they take one of the addresses you've
seen.

It is possible to take action if the address is in the 169.254 subnet.
You write "...is it possible to quit". What exactly did you have in
mind?

 

[GWB]

OK, should have read more. Now I see that this was Microsofts idea of what
to do when the DHCP server isn't working.

It looks like a possible workaround is to disable/enable NIC while I am
trying to convince Linksys it is their router. I probably should just give
up and buy a new wireless router. The new MIMO routers seem better suited
anyhow, its just the principle now.

GWB

 

[Marcel]

OK, should have read more. Now I see that this was Microsofts idea of what
to do when the DHCP server isn't working.

It looks like a possible workaround is to disable/enable NIC while I am
trying to convince Linksys it is their router. I probably should just give
up and buy a new wireless router. The new MIMO routers seem better suited
anyhow, its just the principle now.

The IP thing is called APIPA (Automatic Private IP Adressing). I know it can
be disabled but don't know how to do that, google does. A workaround is
quite simple, let the dhcp server in your router distribute ip's in the
169.254.x.y range. If the clients drop to apipa, everything is still
working. You will only notice it when you want to use the Internet and
receive 404's.

 

[SIME U via WinServerKB.com]

Hi

The APIPA address is assigned because in the "alternate configuration" tab in
TCP/IP propties you have "use automaic private IP addressing" enabled

Therefore when your clients cant receive a DHCP lease from your DHCP server
it failover to the auto range which is 169.254.x.x

Just put a static IP in the right range of your DHCP in the alternate config
and you wont get the APIPA addresses anymore

note sure if using the router to distribute IP in the APIPA range is a good
idea?

Regards

Si

OK, should have read more. Now I see that this was Microsofts idea of what
to do when the DHCP server isn't working.

[quoted text clipped - 3 lines]

up and buy a new wireless router. The new MIMO routers seem better suited
anyhow, its just the principle now.

The IP thing is called APIPA (Automatic Private IP Adressing). I know it can
be disabled but don't know how to do that, google does. A workaround is
quite simple, let the dhcp server in your router distribute ip's in the
169.254.x.y range. If the clients drop to apipa, everything is still
working. You will only notice it when you want to use the Internet and
receive 404's.