Sign in with
Sign up | Sign in
Your question

HP Pavilion a330n - No Network Connectivity

Last response: in Systems
Share
March 14, 2011 2:12:53 PM

Got an old computer from a client to fix up this past weekend.
OS: Windows XP Home SP1 (I updated it to SP3)

Original Problem: The Code Purple error on boot:
I did the Code Purple hack and got it to boot to a desktop.

Now the problem I'm having is that it seems I'm not connected to my network.
It's getting an IP address, Gateway, and DNS from DHCP server.
I even tried it with a static IP address.
I went through the Windows XP network configuration like 100 times and tried
every possible combination, but still no network or Internet. The stupid network wizard wanted
to connect to my network through the fire fire port, so I disabled it in the BIOS so it only shows
the LAN.

I updated the BIOS, I updated the NIC drivers (nForce MCP network controller).

I downloaded Service Pack 3 from another computer and updated the computer to that to.

When I try to ping from it, it can't find anything.
My DHCP server sees the computer, but I can't access or ping it from any other computers on my network.

Firewall is disabled.

The Network Status is reporting packets sent but ZERO packets received.

The computer was just restored to factory settings and everything so there are no viruses or trojans just a bunch of stupid bloatware that I uninstalled.

My new theory is that either HP's branded OS is not letting me connect to a network because the OS's that caused the Code Purple error in the first place was FUBAR'd or the NIC is bad.

Just wondering if anyone has every encountered anything like this before?
It would save me a lot of time if I didn't have to re-format the stupid thing with Windows XP Pro,
which was what I should have done first, but the DVD/CD rom doesn't work in the damn thing
and I don't have a spare IDE DVD/CD rom and don't want to purchase one just to fix up this stupid
outdated computer.

I have a spare Wireless NIC somewhere that I can not find at the moment, but will try that as soon as I find it.
March 14, 2011 3:44:14 PM

I think you solved your own question, sounds like a bad NIC. Check for the lights on the back and check the RJ45 cable you're using for broken connections.
m
0
l
March 14, 2011 3:54:45 PM

HPrometheus said:
I think you solved your own question, sounds like a bad NIC. Check for the lights on the back and check the RJ45 cable you're using for broken connections.



Lights are flashing.
Can a NIC be bad even though it's getting an IP address and everything?
m
0
l
Related resources
March 14, 2011 4:12:06 PM

99.9% of the problems are in the wiring usually. Maybe look at security settings? Sounds like what you'd get if the password was wrong on a wireless network...

Still getting an IP means you're on the local network, are you pinging another computer ont eh network?
m
0
l
March 14, 2011 5:53:25 PM

HPrometheus said:
99.9% of the problems are in the wiring usually. Maybe look at security settings? Sounds like what you'd get if the password was wrong on a wireless network...

Still getting an IP means you're on the local network, are you pinging another computer ont eh network?


This computer is on my build bench. The wiring is good because it works on every other computer and laptop on my build bench. I can't ping out or to this computer. Very bizarre. If this is a symptom of a bad NIC then it's the first time in my 15 years of fixing and building computers that I've come across this.
m
0
l
March 14, 2011 6:25:17 PM

I'm CCNA certified, and I'm baffled. Maybe a router setting? Gosh, it's ratting me.
m
0
l
March 15, 2011 4:24:26 AM

I figured out the problem. It was a bad NIC. Told the client the bad news and now he doesn't want to fix it anymore. The thing was a piece of *** anyways, good thing I don't have to deal with that old computer anymore. It wasted almost a day of my life.
m
0
l
!