The fact that it used to work doesn't mean it always will. It was never
supposed to work and using the fact that it sometimes worked was a mistake.
You would be much better off to redesign the network properly so it doesn't
break again in the future.
"169.254.0.0/16 - This is the "link local" block. It is allocated for
communication between hosts on a single link. Hosts obtain these
addresses by auto-configuration, such as when a DHCP server may
not be found."
http://tools.ietf.org/html/rfc3330
--
Kerry Brown
Microsoft MVP - Shell/User
www.vistahelp.ca/phpBB2
"Andreas Wruhs" <aw@taonet.at> wrote in message
news:ezT$uh3JHHA.448@TK2MSFTNGP04.phx.gbl...
> We know all of that - but du you know how to enable the routing or not? -
> In 2000, XP, 2003 it works!!
>
> "AJR" <ajrjdr@comcast.net> schrieb im Newsbeitrag
> news:eD6TIdrJHHA.1252@TK2MSFTNGP02.phx.gbl...
>> IPs in the 169 (private addresses) set are automatically assigned by
>> Windows when DHCP not available. With 169 addresses, computers can only
>> communication within their network - they have no access outside of their
>> network (public IPs required - such as 192.*.*.*).
>>
>> "Andreas Wruhs" <aw@taonet.at> wrote in message
>> news:ONQsgymJHHA.4000@TK2MSFTNGP06.phx.gbl...
>>> Hi there
>>>
>>> does somebody know how to enable routing of ip ranges in the 169.254.x.x
>>> subnet over the default gw?
>>> when we manually add a route via the cmd all is functional but it seems
>>> that ms disabled the automatic routing of APIPA range over the default
>>> gw!
>>>
>>> thnxs andi
>>>
>>
>>
>
>