Posted by Holy Schmoly on May 29, 2009, 3:19 pmPlease Register and login to reply and use other advanced options
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
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,
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
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
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  **********
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  **********
SnmpStatInit: Not supported on Windows 2000+.
ERROR: No compatible network interfaces were found.
Posted by kony on May 29, 2009, 5:04 pm
On Fri, 29 May 2009 13:19:26 -0600, Holy Schmoly <> wrote:
Power surges are a common cause of network adapter failure.
However you did not state what the mobo's nic is connecting
to on the other end of the cable. I have seen cases where
it was the equipment on the other end, just one port on a
network hub or switch, presumably it could happen to a
router/modem/etc too, that blew out... or perhaps more than
one port, depending on what was connected (if anything) to
the other ports.
Therefore I suggest you check the link lights on both ends
of the cable, unplug the cable from the mobo and inspect the
contacts on both the cable connector and nic socket then
plug them back in. Do the same for the other end of the
cable and if you have another port on the other end,
especially one that was not being used at the time of the
power anomoly, plug the cable into that port instead. Next
power cycle this other piece of equipment.
Did the power anomoly cause the computer to reboot or did
you manually do that and/or turn it off and on again since
then? If not, reboot the system. You might try that before
fiddling with the cable as mentioned previously.
Does the network adapter still show up in Device Manager and
if so, is there an exclamation mark indicating a problem?
If there is none listed in Device Mgr or an exclamation
mark, no point in fiddling with the cabling as mentioned
initially, you have a software problem or perhaps hardware
logic circuit damage.
While files that are open may become corrupted during system
instability or crash/reboot, files that are static, merely
read by the OS for use after installation are not likely to
be corrupted or lost unless the entire filesystem becomes
corrupt which it seemingly didn't since the system otherwise
works. Therefore I suggest these kinds of attempts aren't
likely to fix the problem.
I should read ahead before replying more often. :-)
At this point I'd probably just buy a new NIC, preferribly
PCIe if you have a free slot for that type, though the old
PCI ones are probably still cheaper and if you don't need
max GbE performance it should suffice.
The bad news is if a surge went further than the network
controller chip or there were concurrent surge paths through
other subcircuits on the motherboard, then other motherboard
features may be more subtly damaged or fail later.
If this is a home, personal use system not used for anything
critical, I would take a wait-n-see attitude about the state
of the rest of the motherboard. If it is instead a business
or otherwise critical system I would go ahead and replace
the entire motherboard. A replacement can be found for
about $70 delivered at places like Newegg...
... though if you felt like reinstalling windows then you
might prefer a more modern board as it would typically
result in slightly better performance from improved memory
throughput, possibly more rear panel USB or audio ports,
faster integrated video (possibly capable of HD decoding on
GPU too, and possibly DVI or HDMI video output), and other
features. What a newer board would potentially no longer
support is either or both PS2 ports, parallel and/or serial
I seem to have drifted off on a tangent, trying a new NIC is
the easiest low cost option unless someone else has more OS
Posted by GlowingBlueMist on May 29, 2009, 7:37 pm
Holy Schmoly wrote:
This would be a good place to try booting one of those Linux Live CD's and
see if that operating system also has a problem with your interface.
If the alternate OS fails to find a working interface you might also go into
your BIOS and regardless of it's current state, disable the internal
interface, save the change and reboot the system, then go back into the BIOS
and turn the interface back on, save the change and reboot again. Then I'd
try either OS but the Live Linux CD would be my first choice just in case
the Windows OS has been corrupted either by the power spike or subsequent
attempts at a fix.
Posted by Andy on May 30, 2009, 9:32 pm
Please Register and login to reply and use other advanced options
- Posted In
- system error: An internal error occurred: the request is not suppo
- Microsoft Windows MediaCenter
- Subscribe via RSS