Me PC TCP/IP Stack not working for LAN card

Hello - Sherlock Holmes, are you out there and ready for
this one ?

I have a good networking knowledge base and my WINme PC is
funky. I config it for DHCP (obtain IP address) and it
always gets the automatic private IP address
(169.254.x.x). {meaning DHCP server not reachable...I
know!}

Three other XP machines and my work WIN2000 machine get
addresses just fine from my wireless router. WINIPCFG just
times out when trying to release/renew and says "Error -
DHCP server unavailable: renewing adapter". I tried a
brand new Ethernet card and same problem.

I tried to ping this sick machine from an XP box, and it
(XP box) got the MAC address in its ARP cache, but the
ping failed....sounds like Windows TCP/IP stack is the
weak link. I can ping 127.0.0.1 on my machine too, but
nothing outside of the box.

I have also tired removing the HW driver and TCP client,
and reinstall with same problem. I just fixed another
windows update issues and are all up to date. Even got a
new BIOS load from HP.

In article <007401c39e9a$c960eab0$(E-Mail Removed)>, "Jeff Anderson"
<(E-Mail Removed)> wrote:
>Hello - Sherlock Holmes, are you out there and ready for
>this one ?
>
>I have a good networking knowledge base and my WINme PC is
>funky. I config it for DHCP (obtain IP address) and it
>always gets the automatic private IP address
>(169.254.x.x). {meaning DHCP server not reachable...I
>know!}
>
>Three other XP machines and my work WIN2000 machine get
>addresses just fine from my wireless router. WINIPCFG just
>times out when trying to release/renew and says "Error -
>DHCP server unavailable: renewing adapter". I tried a
>brand new Ethernet card and same problem.
>
>I tried to ping this sick machine from an XP box, and it
>(XP box) got the MAC address in its ARP cache, but the
>ping failed....sounds like Windows TCP/IP stack is the
>weak link. I can ping 127.0.0.1 on my machine too, but
>nothing outside of the box.
>
>I have also tired removing the HW driver and TCP client,
>and reinstall with same problem. I just fixed another
>windows update issues and are all up to date. Even got a
>new BIOS load from HP.

How did you try to ping the sick machine from XP? What IP address did
XP have, and what IP address did you ping? What did the error message
say when it failed?

Disable and un-install all firewall programs on the sick machine while
troubleshooting. Then, go to Start | Run | Msconfig | Startup,
disable any firewall remnants, and reboot.

Try explicitly setting the Ethernet network card's speed and duplex
mode. Automatic sensing sometimes fails.

Try a different router port. Try a different cable.
--
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 - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

did you attempt to dump your tcp/ip stack? Sometimes it
does help. In order to do this, in the run bar type
netsh dump then press enter