|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
May 29th 09, 08:21 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
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/in...t=#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. 
|
| Ads |
|
#2
May 29th 09, 08:45 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
A UPS is a wonderful thing to have when there are power glitches.
Holy Schmoly wrote in message ... : 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/in...t=#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.
|
|
#3
May 29th 09, 08:45 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
A UPS is a wonderful thing to have when there are power glitches.
Holy Schmoly wrote in message ... : 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/in...t=#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.
|
|
#4
May 29th 09, 09:43 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query hostname.)
On May 29, 8:45*pm, "Tom Willett" wrote:
A UPS is a wonderful thing to have when there are power glitches.Holy Schmoly wrote in message ... : 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/in...743&pid=162308... : : 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. Unfortunately, no one ever believes that these power glitches will happen to them. A UPS is the best protect but the UPS should have power filtering.
|
|
#5
May 29th 09, 09:43 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query hostname.)
On May 29, 8:45*pm, "Tom Willett" wrote:
A UPS is a wonderful thing to have when there are power glitches.Holy Schmoly wrote in message ... : 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/in...743&pid=162308... : : 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. Unfortunately, no one ever believes that these power glitches will happen to them. A UPS is the best protect but the UPS should have power filtering.
|
|
#6
May 30th 09, 06:37 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
"smlunatick" wrote in message
... On May 29, 8:45 pm, "Tom Willett" wrote: A UPS is a wonderful thing to have when there are power glitches.Holy Schmoly wrote in message ... : 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/in...743&pid=162308... : : 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. Unfortunately, no one ever believes that these power glitches will happen to them. A UPS is the best protect but the UPS should have power filtering. ===================== Many years ago, I worked next to a group that supported a very popular fax product. One day a fax appeared on the lunch room wall - it was an apology from a customer who had been perhaps less than politely adamant that the problems he was having were software related, and couldn't *possibly* be the modem. One night, the question was settled by a lightning strike that literally fried the modem via the telephone line. And after he cleard the charred bits out and installed a NEW MODEM, the previously "defective" software magically began working as advertised. The saying for lightning strikes is that surge protection is nice to have, a UPS is good, but the lightning just travelled perhaps miles through open air, and a few more inches along a wire won't slow it at all.
|
|
#7
May 30th 09, 06:37 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
"smlunatick" wrote in message
... On May 29, 8:45 pm, "Tom Willett" wrote: A UPS is a wonderful thing to have when there are power glitches.Holy Schmoly wrote in message ... : 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/in...743&pid=162308... : : 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. Unfortunately, no one ever believes that these power glitches will happen to them. A UPS is the best protect but the UPS should have power filtering. ===================== Many years ago, I worked next to a group that supported a very popular fax product. One day a fax appeared on the lunch room wall - it was an apology from a customer who had been perhaps less than politely adamant that the problems he was having were software related, and couldn't *possibly* be the modem. One night, the question was settled by a lightning strike that literally fried the modem via the telephone line. And after he cleard the charred bits out and installed a NEW MODEM, the previously "defective" software magically began working as advertised. The saying for lightning strikes is that surge protection is nice to have, a UPS is good, but the lightning just travelled perhaps miles through open air, and a few more inches along a wire won't slow it at all.
|
|
#8
May 30th 09, 02:05 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
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 ... 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/in...t=#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.
|
|
#9
May 30th 09, 02:05 PM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
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 ... 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/in...t=#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.
|
|
#10
June 2nd 09, 12:15 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
On Sat, 30 May 2009 09:05:01 -0400, "SC Tom" wrote:
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. The PC in question is connected through a Linksys WRT54G router and yeah, I've verified that the modem's good using my laptop. The port at the back of my PC is also good and I also get the light coming on when plug the ethernet cable into the onboard NIC port in the back of my PC. 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. 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? 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 .. . 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/in...t=#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.
|
|
#11
June 2nd 09, 12:15 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
On Sat, 30 May 2009 09:05:01 -0400, "SC Tom" wrote:
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. The PC in question is connected through a Linksys WRT54G router and yeah, I've verified that the modem's good using my laptop. The port at the back of my PC is also good and I also get the light coming on when plug the ethernet cable into the onboard NIC port in the back of my PC. 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. 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? 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 .. . 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/in...t=#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.
|
|
#12
June 2nd 09, 03:39 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
If you disable the onboard NIC in BIOS, you should be able to remove those
items in Device Manager. Just because the NIC light comes on doesn't mean it works. The WAN miniports are hidden devices (at least they are on my PC); installing a new NIC, if necessary, shouldn't be hampered by them. They were present with my onboard NVIDIA NIC, and are still there with my Realtek NIC. SC Tom Holy Schmoly wrote in message news  On Sat, 30 May 2009 09:05:01 -0400, "SC Tom" wrote: 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. The PC in question is connected through a Linksys WRT54G router and yeah, I've verified that the modem's good using my laptop. The port at the back of my PC is also good and I also get the light coming on when plug the ethernet cable into the onboard NIC port in the back of my PC. 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. 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? 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 . .. 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/in...t=#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.
|
|
#13
June 2nd 09, 03:39 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
If you disable the onboard NIC in BIOS, you should be able to remove those
items in Device Manager. Just because the NIC light comes on doesn't mean it works. The WAN miniports are hidden devices (at least they are on my PC); installing a new NIC, if necessary, shouldn't be hampered by them. They were present with my onboard NVIDIA NIC, and are still there with my Realtek NIC. SC Tom Holy Schmoly wrote in message news On Sat, 30 May 2009 09:05:01 -0400, "SC Tom" wrote: 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. The PC in question is connected through a Linksys WRT54G router and yeah, I've verified that the modem's good using my laptop. The port at the back of my PC is also good and I also get the light coming on when plug the ethernet cable into the onboard NIC port in the back of my PC. 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. 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? 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 . .. 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/in...t=#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.
|
|
#14
June 2nd 09, 04:36 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
OK, I think I'll just end up installing a new NIC and it's good to
hear that those items with the yellow exclamation marks. For some reason though, I'm not able to remove them even though I've disabled the onboard NIC in the BIOS. Oh, well, a trip to a computer shop tomorrow. Thanks for all your help and time into this matter, SC Tom! On Mon, 1 Jun 2009 22:39:29 -0400, "SC Tom" wrote: If you disable the onboard NIC in BIOS, you should be able to remove those items in Device Manager. Just because the NIC light comes on doesn't mean it works. The WAN miniports are hidden devices (at least they are on my PC); installing a new NIC, if necessary, shouldn't be hampered by them. They were present with my onboard NVIDIA NIC, and are still there with my Realtek NIC. SC Tom Holy Schmoly wrote in message news On Sat, 30 May 2009 09:05:01 -0400, "SC Tom" wrote: 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. The PC in question is connected through a Linksys WRT54G router and yeah, I've verified that the modem's good using my laptop. The port at the back of my PC is also good and I also get the light coming on when plug the ethernet cable into the onboard NIC port in the back of my PC. 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. 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? 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 ... 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/in...t=#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.
|
|
#15
June 2nd 09, 04:36 AM
posted to microsoft.public.windowsxp.hardware
|
|||
|
|||
|
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
OK, I think I'll just end up installing a new NIC and it's good to
hear that those items with the yellow exclamation marks. For some reason though, I'm not able to remove them even though I've disabled the onboard NIC in the BIOS. Oh, well, a trip to a computer shop tomorrow. Thanks for all your help and time into this matter, SC Tom! On Mon, 1 Jun 2009 22:39:29 -0400, "SC Tom" wrote: If you disable the onboard NIC in BIOS, you should be able to remove those items in Device Manager. Just because the NIC light comes on doesn't mean it works. The WAN miniports are hidden devices (at least they are on my PC); installing a new NIC, if necessary, shouldn't be hampered by them. They were present with my onboard NVIDIA NIC, and are still there with my Realtek NIC. SC Tom Holy Schmoly wrote in message news On Sat, 30 May 2009 09:05:01 -0400, "SC Tom" wrote: 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. The PC in question is connected through a Linksys WRT54G router and yeah, I've verified that the modem's good using my laptop. The port at the back of my PC is also good and I also get the light coming on when plug the ethernet cable into the onboard NIC port in the back of my PC. 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. 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? 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 ... 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/in...t=#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.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
