Windows XP-Realtek 8139 ethernet adapters

  • Thread starter Thread starter trisher01
  • Start date Start date
T

trisher01

Just curious if anyone else has come across an issue with
the realtek nic's and windows xp. I work for a broadband
isp and consistently with realtek 8139 nics and windows xp
the dhcp address comes up as 169.254.x.x. If another nic
is inserted it picks up the ip address as it should from
our servers. The ip address passes through the broadband
cable modem first then to the pc. Only with the realtek
8139 nic does this occur. It does not matter whether or
not a service pack is installed. Any ideas are most
welcome. thanks.
 
All I know is that this is not an issue directly related to the 8139 cards,
I have also seen it with ADMTek, Eicon, 3com and Broadcom NICs just to name
a few off the top of my head. The issue is actually within Windows, just
about always the issue can be resolved by reinstalling Windows, but I'm sure
there must be a simpler fix, I would very much like to know if anybody could
tell me about this, I believe that the address is some sort of 'private'
address given to the card by Windows when DHCP requests fail in some
particular cases, but why exactly or when exactly this occurs I am unsure.

Regards, Wichetael.
 
The address is an APIPA address. It is what is given when
no DHCP server can be reached. This is a standard feature
within windows. However, I'm referencing the 8139 cards
because as I said in my original question, they can pull
out the card, insert another, and it works fine. They re-
insert the realtek and 169 again. I've had several
customers try this.
 
Yeah, I understand what you meant and I experienced exactly the same thing
with cards of other brands... insert another card and it seems to work fine
again, insert the original card again and it messes up again... I'm thinking
Windows somehow fudges up something in the TCP/IP stack coupling with the
network card driver or possible the driver itself...
 
Back
Top