AD server not responding - hardware error

My AD (user authentication only) server returns a hardware error whenever I try to ping anything.  Has anyone seen this before, if so is there any fix?  

It is an old windows server 2003 R2 box.  Purchased back in 2007.
LVL 31
Thomas Zucker-ScharffSystems AnalystAsked:
Who is Participating?
 
Thomas Zucker-ScharffConnect With a Mentor Systems AnalystAuthor Commented:
Turned out it wasn't the NIC.  After checking with crossover cable it turned out to be the network jack (thought this wad okay as more than one device is plugged in there).
0
 
FOXActive Directory/Exchange EngineerCommented:
what is the exact error it is throwing?
0
 
Thomas Zucker-ScharffSystems AnalystAuthor Commented:
on the ping it just says "Hardware error" and no packets are received.  I just looked at the physical setup inside the machine and the network card is built into the motherboard (argh).  There is not activity showing (normally flashing lights).  I have attached an audit of the machine I did over a year ago.
AECCCSERVE.pdf
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
FOXActive Directory/Exchange EngineerCommented:
Do you have any available pci slots to add another nic?  Have you tried installing new drivers for the onboard nic?
0
 
Thomas Zucker-ScharffSystems AnalystAuthor Commented:
Haven't tried installing new drivers.  I have a couple of slots.  Will it take any NIC?
0
 
MacleanSystem EngineerCommented:
Best is to use a NIC supported by the Vendor. If under warranty, log a call with them.
It does sound like a NIC problem.

You could try re-installing the drivers as suggested.
In addition I would assume most NIC's would work if there is a driver for the OS in question available, but always best to stick to Vendor Supported NIC's

Could also try running the command line netsh reset winsock, but judging by the error, this probably won't do much.
0
 
Thomas Zucker-ScharffSystems AnalystAuthor Commented:
thanks working on it now
0
 
MacleanSystem EngineerCommented:
Ok. Don't forget to apply the same IP details to the NIC as the original, once the original had IP removed and NIC disabled if this is the path you are taking.
0
 
Thomas Zucker-ScharffSystems AnalystAuthor Commented:
I have been looking for an extra NIC to put in there and have not found one "lying" around.  I am looking at the docs for using the diagnostic tools.

Thanks
0
 
MacleanSystem EngineerCommented:
If the existing NIC is not build into the mainboard, try moving it into another slot with the computer powered down.

Try a newer or older driver for the NIC as suggested by others,or try re-seating the NIC as per above suggestion, plus reset the winsock as per my earlier suggestion.

Worst case, call your vendor for warranty support. They usually send a tech out same day depending on your maintenance contract. Which is where the warranty value kicks in :)
0
 
Thomas Zucker-ScharffSystems AnalystAuthor Commented:
There was really no solution to this problem.  Foxluv had the best suggestions.  And since this was only being used as an authentication server, I am retiring it.
0
 
MacleanSystem EngineerCommented:
Ok, going to guess it was the NIC, but I see your point :) Don't forget to demote it from the AD if it was a AD DC server. Good luck.
0
 
Thomas Zucker-ScharffSystems AnalystAuthor Commented:
Due to the initial lack of information, I do not believe anyone could have come up with the eventual solution.  A colleague of mine did say, "Did you try a crossover cable to test the NIC?"  He was right on target.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.