Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)

Holy Schmoly wrote:
On Fri, 29 May 2009 19:23:54 -0400, Paul <nospam@xxxxxxxxxx> wrote:

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.)

I've uninstalled DUMeter and I'm able to uninstall my NIC from my
Device Manager, but when I try to uninstall the rest of the things
listed under Network adapters, such as 1384 Net adapter
Direct Parallel
Realtek RTL8168/8111 PCI-E Gigabit - Packet Scheduler Miniport
WAN Miniport (IP)
WAN Miniport (IP) - Packet Scheduler Miniport
WAN Miniport (L2TP)
WAN Miniport (Network Monitor)
WAN Miniport (Network Monitor) - Packet Scheduler Miniport
WAN Miniport (PPPOE) and
WAN Miniport (PPTP)

When I double click on them to bring up the Properties for each, the
Device Status for all of them in the General tab says, "Windows cannot
load the device driver for this hardware. The driver may be corrupted
or missing (code 39).

Realtek's driver installation program has an option to remove whatever
it installs, so I tried that, but the same thing happens.

I would go and just pick up a new NIC, but what concerns me is that I
can't properly delete all those things first before I slap a new NIC
in my computer.

Any ideas?


I can find some hits for the WAN ones. I see mention of VMWare. There
is also a Nortel product mentioned here. (The 1394 is part of Windows,
and you can build networks over Firewire. If you connected two computers
with a Firewire cable, and weren't running Vista, you could network across
that link.)

http://communities.vmware.com/thread/174958?tstart=0

I haven't a clue what you do next.

Paul
.

Relevant Pages

  • Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
    ... show up in Network Connections, ... Reboot and check Device Manager again to be sure it ... WAN Miniport - Packet Scheduler Miniport ... Realtek's driver installation program has an option to remove whatever ...
    (microsoft.public.windowsxp.hardware)
  • Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
    ... NIC driver files are stored, ... power down the PC, plug the network cable back in, boot up to Windows ... WAN Miniport - Packet Scheduler Miniport ... Realtek's driver installation program has an option to remove whatever ...
    (microsoft.public.windowsxp.hardware)
  • RE: WAN Miniport
    ... > driver listed in C:\windows\driver cache ... Since the icon for the WAN Miniport in Device Manager has a ... My home wireless network is working fine; is this related to the WAN? ...
    (microsoft.public.windowsxp.general)
  • Re: I need help
    ... 'dne2000.sys' is deterministic network enhancer (which you likely don't need ... malfunctioning network component in the Windows Device Manager, ... driver, restart Windows. ...
    (microsoft.public.windowsxp.device_driver.dev)
  • Re: wireless network adapter
    ... >install a new driver for the adapter, but have been unable to do so. ... >Device Manager, when I select the folder with the new driver, I get a message ... all instances of the network adapters. ...
    (microsoft.public.windowsxp.configuration_manage)