APIPA on Multihomed Client

[JoeB]

I have a client (multihomed) connected to a DHCP enabled
network, and connected to another client via crossover.
Crossover NIC is being assigned 169.254.x.x on both clients
(good), and the NIC connected to the network has a 9.x.x.x
(good). In some cases, the multihomed client cannot, will
not, send TCP packets to the crossover, unless I make the
the 9.x.x.x static, OR , I assign the crossover NIC an IP
address other than 169.254.x.x. This has happend on both
XP and 2K.
Has anyone heard that APIPA will not work correctly if
DHCP is enabled on both NICs on a multihomed client?

Thanks
JoeB

 

[Steve Winograd [MVP]]

I have a client (multihomed) connected to a DHCP enabled
network, and connected to another client via crossover.
Crossover NIC is being assigned 169.254.x.x on both clients
(good), and the NIC connected to the network has a 9.x.x.x
(good). In some cases, the multihomed client cannot, will
not, send TCP packets to the crossover, unless I make the
the 9.x.x.x static, OR , I assign the crossover NIC an IP
address other than 169.254.x.x. This has happend on both
XP and 2K.
Has anyone heard that APIPA will not work correctly if
DHCP is enabled on both NICs on a multihomed client?

Thanks
JoeB

I suspect that the NIC connected to the network sometimes fails to
contact a DHCP server to get a 9.x.x.x address. When that happens, it
would assign itself an APIPA address. That would mean that both NICs
have 169.254.x.x IP addressees, which is certain to cause problems
with packet routing.
--
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

 

[JoeB]

-----Original Message-----

I suspect that the NIC connected to the network sometimes fails to
contact a DHCP server to get a 9.x.x.x address. When that happens, it
would assign itself an APIPA address. That would mean that both NICs
have 169.254.x.x IP addressees, which is certain to cause problems
with packet routing.
--
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
.

Thanks Steve for replying. I am 99 44/100% sure the NIC
to the network does indeed have its 9.x.x.x address at the
time of my problem. Is it possible, although the routing
table looks fine, by some configuration I don't know
about, that, any address starting with 169.254 is
attempting to use the 0.0.0.0 network destination adress?
Is there a search order? Thanks.

JoeB