Vista - APIPA not using supplied custom address

I've noticed that Vista seems to not always use the custom supplied IP
address when APIPA is used. In XP this always worked fine and Windows would
never use a 169.x.y.z system generated address if a custom IPv4 address is
supplied. In Vista, on odd occasions it creates a system gen 169 address when
it should never do so - the system is configued to use an address I supplied
not generate one.

Does anyone know if this would be a bug or a setting issue ???

In article <EFF1B4B8-C12C-4F56-AFE3-C9007748AF38@microsoft.com>,
gslender <gslender@discussions.microsoft.com> wrote:
>I've noticed that Vista seems to not always use the custom supplied IP
>address when APIPA is used. In XP this always worked fine and Windows would
>never use a 169.x.y.z system generated address if a custom IPv4 address is
>supplied. In Vista, on odd occasions it creates a system gen 169 address when
>it should never do so - the system is configued to use an address I supplied
>not generate one.
>
>Does anyone know if this would be a bug or a setting issue ???

How do you specify a custom supplied IP address for use with APIPA in
XP and Vista?

Do you mean the user configured address on the Alternate Configuration
tab of the TCP/IP properties?
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Yes,

On the Alternate Configuration tab you can specify a User Configured IP
address.

Help page for that tab says....

User configured specifies that IPv4 use a manually specified configuration
if a DHCP server is not found. This alternate configuration is useful when
the computer is used on more than one network, at least one of the networks
does not have a DHCP server, and an APIPA configuration is not wanted. A good
example is a portable computer that is used at the office and at home. At the
office, the laptop uses a DHCP-allocated TCP/IP configuration. At home, where
there is no DHCP server present, the portable computer automatically uses the
alternate configuration, allowing easy access to home network devices and the
Internet. This enables the portable computer to operate seamlessly on both
networks without manual IP reconfiguration.


"Steve Winograd [MVP]" wrote:

> In article <EFF1B4B8-C12C-4F56-AFE3-C9007748AF38@microsoft.com>,
> gslender <gslender@discussions.microsoft.com> wrote:
> >I've noticed that Vista seems to not always use the custom supplied IP
> >address when APIPA is used. In XP this always worked fine and Windows would
> >never use a 169.x.y.z system generated address if a custom IPv4 address is
> >supplied. In Vista, on odd occasions it creates a system gen 169 address when
> >it should never do so - the system is configued to use an address I supplied
> >not generate one.
> >
> >Does anyone know if this would be a bug or a setting issue ???
>
> How do you specify a custom supplied IP address for use with APIPA in
> XP and Vista?
>
> Do you mean the user configured address on the Alternate Configuration
> tab of the TCP/IP properties?
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>