Re: Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
- From: "SC Tom" <sc@xxxxxxx>
- Date: Sat, 30 May 2009 09:05:01 -0400
Now that everyone has told you what you SHOULD have done, let's try a few
things.
Disable DUMeter.
Are you connected through a cable modem to the internet? If so, do you have
a notebook or other PC you can use to verify that it's good? If it's
blasted, it may be dragging down or has shorted out your onboard NIC.
If the modem is good, unplug your network cable, boot into BIOS, and disable
the onboard NIC. Save changes and exit and boot into Windows. Open Device
Manager and see if it is listed. If it is, uninstall/delete it. It shouldn't
show up in Network Connections, but double-check there and see. If by chance
it does, delete it. Reboot and check Device Manager again to be sure it
hasn't reappeared.
Reboot back into BIOS and re-enable the onboard NIC. Save changes and boot
into Windows. Found New Hardware should appear- point it to wherever your
NIC driver files are stored, and let it install. After the installation,
power down the PC, plug the network cable back in, boot up to Windows and
see if it all works. If not, it's probably the NIC.
If your cable modem supports a USB connection, you can use it instead of
purchasing another NIC. It's not as fast, but is usually adequate. PCI NIC's
can be had for $15 or so if you have an open slot. Be sure to disable the
onboard NIC in BIOS before installing either.
I have found in my personal experience that the onboard NIC's seem to be
very fragile- I haven't had one last more than 18 months or so before it
started giving me problems. And I have about as much power and line
protection that can be had LOL.
SC Tom
<Holy Schmoly> wrote in message
news:tad025p6l15a0608v47v4ecjqolkkbn0aq@xxxxxxxxxx
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.
.
- Prev by Date: Re: Microsoft Wireless Keyboard 3000
- Next by Date: Re: 1394 IEEE was working
- 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
|
