Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
- From: Paul <nospam@xxxxxxxxxx>
- Date: Fri, 29 May 2009 19:23:54 -0400
Holy Schmoly wrote:
My computer was working just fine until there was a split second power
outage in my area. Everything shut off, but then all came back in a
matter of a second.
After that, I powered up my computer and I'm not able to get online at
all since. When I perform ipconfig with or without any flags, I get
this message:
Windows IP Configuration
An internal error occurred: The request is not supported.
Please contact Microsoft Product Support Services for further help.
Additonal information: Unable to query host name.
In my Start->Settings->Control Panel->Network Connections, I don't see
the network icon which was associated with the properly functioning
network before all this happened.
I searched and searched and tried a few things already. I performed a
console recovery following the instructions put forth here,
http://forums.scotsnewsletter.com/index.php?showtopic=9743&pid=162308&mode=threaded&start=#entry162308
But didn't work for me, even though the OP had the exact same error
message with his ipconfig.
I also reset the WINSOCK entries to installation defaults using "netsh
winsock reset catalog" and also reset TCP/IP stack to installation
defaults with "netsh int ip reset reset.log" but to no avail.
When I look in Device Manager, my onboard NIC has the yellow
exclamation mark beside and I've uninstalled it and rebooted and cold
booted and reinstalled the drivers for it, but I still have the
exclamation mark.
I'm really at a loss here with this problem and was wondering if
anyone's ever experienced something like this and am looking for some
input, suggestions or insight into this matter. Thanks for your time
and courtesy.
My mobo's an Asus P5B-VM with a Realtek RTL8168/8111 PCI-E Gigabit
Ethernet onboard NIC.
Oh, another thing, I use an app which monitors my bitusage called
DUMeter and when it starts, it gives this error message:
********** PROBING DATA COLLECTION METHOD [0] **********
C:\WINDOWS\system32\IpHlpApi.dll version: Description: IP Helper API
File version: 5.1.2600.2912 (xpsp.060519-0015)
Product version: 5.1.2600.2912
IpHlpStatInit: Interface table size is zero.
********** PROBING DATA COLLECTION METHOD [1] **********
SnmpStatInit: Not supported on Windows 2000+.
ERROR: No compatible network interfaces were found.
The fact that your Device Manager shows a problem, tells you there
is no need to try higher level tests. If the driver won't load,
higher level networking commands aren't going to work. So you've
zeroed in on the right issue, which is getting some driver to
load.
You might consider uninstalling DUMeter, before attempting to fix
the RealTek driver. Your DUMeter would be using a "shim", like
an UpperFilter/LowerFilter driver, to gain access to the network
information stream. Maybe if that software was temporarily uninstalled,
you can get the driver put back in there. (I'm not saying for certain,
that a filter driver makes a difference, but it might not be
something the RealTek installer is expecting.)
*******
You could test the hardware, by using a Linux LiveCD. A LiveCD doesn't
need to install any software, and runs from the CD. It uses the system
memory as a RAM disk, for temporary storage. I use Knoppix for
maintenance work on my computer, and have collected several different
versions of CD. The size of the downloads is an issue though, so
for people on dialup, this isn't a viable option.
The latest Knoppix dropped the KDE environment, in favor of a new
one. I liked the older one, because it made Windows users more
at home. If you can make some connection to the Internet, using
one of the built-in browsers, then you'd know the RealTek hardware
was OK.
http://www.knopper.net/knoppix/knoppix60-en.html
You could also try taking a spare disk, and doing a clean install
of Windows, then use your motherboard disk to provide drivers.
Do a test ping from the broken computer, to one of your other
computers. I do test installs all the time, with my computer
disconnected from the Internet, long enough to verify hardware.
For example, a couple days ago, I was testing a dual video card,
four monitor setup, without activating WinXP. I keep the
computer disconnected from the Internet, so the computer
won't try to automatically activate or something. I'm running
my "regular" WinXP install at the moment, with the alternate
hardware configuration removed. I could also install
the Win2K I have here, without worrying about activation
(as it doesn't use activation).
If you purchase a UPS, that will help avoid problems caused
by short outages. I have one, because my power utility used
to glitch the power at least once a day. You want to buy
one, above the "bottom tier", for best results. The cheap
ones may not always work correctly.
Paul
.
- Prev by Date: P4S800D-X won't boot off sata
- Next by Date: Re: Computer refuses to boot - plug came loose from the mainboard
- Previous by thread: Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
- Next by thread: Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
- Index(es):
Relevant Pages
|
