Solved

AD server not responding - hardware error

Posted on 2016-09-07
14
146 Views
Last Modified: 2016-09-14
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.
0
Comment
Question by:Thomas Zucker-Scharff
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
  • 2
14 Comments
 
LVL 16

Expert Comment

by:FOX
ID: 41788538
what is the exact error it is throwing?
0
 
LVL 29

Author Comment

by:Thomas Zucker-Scharff
ID: 41788565
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
 
LVL 16

Expert Comment

by:FOX
ID: 41788568
Do you have any available pci slots to add another nic?  Have you tried installing new drivers for the onboard nic?
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 
LVL 29

Author Comment

by:Thomas Zucker-Scharff
ID: 41788588
Haven't tried installing new drivers.  I have a couple of slots.  Will it take any NIC?
0
 
LVL 11

Expert Comment

by:Maclean
ID: 41788610
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
 
LVL 29

Author Comment

by:Thomas Zucker-Scharff
ID: 41788615
thanks working on it now
0
 
LVL 11

Expert Comment

by:Maclean
ID: 41788633
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
 
LVL 29

Author Comment

by:Thomas Zucker-Scharff
ID: 41788670
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
 
LVL 11

Expert Comment

by:Maclean
ID: 41788737
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
 
LVL 29

Author Comment

by:Thomas Zucker-Scharff
ID: 41789530
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
 
LVL 11

Expert Comment

by:Maclean
ID: 41790288
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
 
LVL 29

Accepted Solution

by:
Thomas Zucker-Scharff earned 0 total points
ID: 41790408
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
 
LVL 29

Author Closing Comment

by:Thomas Zucker-Scharff
ID: 41797518
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

Featured Post

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows how to use a free utility called 'Parkdale' to easily test the performance and benchmark any Hard Drive(s) installed in your computer. We also look at RAM Disks and their speed comparisons.
This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question