169 IP problem

[DigitalCancer]

Ok...so I work at this computer shop and we're working on this ladies system (we are also an ISP) and her NIC was hit by lightning (we provide wireless net).

So...we get it in and install a new NIC that was definitely needed, but...she's pulling a 169 IP. Now..it's not the ISP as other computers are plugged into the same connection just fine. I'm trying to keep from formatting her but am running out of ideas and thought maybe someone could suggest something else??

Things tried thus far:

-installed brand new NIC
-disabled the old NIC (onboard) in bios
-netsh int ip reset
-used a winsock xp fix program (basically resets all winsock)
-netsh reset catalog
-uninstalled/reinstalled NIC
-put in IP info for static and it connected fine, but still no net

 

[imported_snikt]

The 169.x.x.x IP address is APIPA. Try this to disable APIPA.

 

[MiniDoom]

is dhcp enabled, or is the dhcp client service running?

 

[spidey07]

I know you've done a lot, but this reaks of a fubarred TCP/IP stack. Certain parts of the stack are working, but others aren't, like DHCP.

Can you ping anything locally when you give a static address? How about pinging by name?

 

[DigitalCancer]

APIPA trick didn't work.

can't ping anything when assigning an IP.

our service does use DHCP.

We gave up just a bit ago though...I believe the only way to really fix this is with a format/reinstall and she'd rather buy a new computer which is always good for us. ^_^

 

[Motorheader]

Was it Windows XP running SP3?? I've run into this 3 times now and the only way to get out of the vicious loop you're on is to uninstall SP3. This has worked 3 times for me in the last 3 weeks. Some recent update in Windows XP seems to be the culprit.

 

[InlineFive]

How about this?