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 |
#16
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
They're yellow now because there are no NIC drivers installed. Once the NIC
and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message ... 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 m... 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 |
#17
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
They're yellow now because there are no NIC drivers installed. Once the NIC
and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message ... 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 m... 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. |
#18
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and
followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message .. . 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 om... 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. |
#19
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and
followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message .. . 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 om... 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. |
#20
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Sorry, forgot to add that, from what I can observe, I think something
is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message . .. 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4ax. com... 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. |
#21
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Sorry, forgot to add that, from what I can observe, I think something
is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message . .. 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4ax. com... 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. |
#22
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Well, I haven't done this in a long time, so I may not remember the steps
entirely. We had a problem at my old job with network cards and connectivity, and IIRC, the fix was to remove TCP/IP and other protocols in network properties, reboot, then reinstall. Not sure if that would work here (probably not), but might be worth a try. Are you showing any errors in event viewer? Might be something there. It's puzzling to me that the drivers won't install. Do you have anything in add/remove programs left over from the old NIC? Have you tried updating your MB drivers? Not the NIC, but the chip set drivers. I'm wondering if maybe the MB was affected by the power flux. Have you tried using system restore to bring it back to a date before the problems started? You may have to do it in safe mode or safe mode w/command prompt. Holy Schmoly wrote in message ... Sorry, forgot to add that, from what I can observe, I think something is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message ... 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4ax .com... 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. |
#23
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Well, I haven't done this in a long time, so I may not remember the steps
entirely. We had a problem at my old job with network cards and connectivity, and IIRC, the fix was to remove TCP/IP and other protocols in network properties, reboot, then reinstall. Not sure if that would work here (probably not), but might be worth a try. Are you showing any errors in event viewer? Might be something there. It's puzzling to me that the drivers won't install. Do you have anything in add/remove programs left over from the old NIC? Have you tried updating your MB drivers? Not the NIC, but the chip set drivers. I'm wondering if maybe the MB was affected by the power flux. Have you tried using system restore to bring it back to a date before the problems started? You may have to do it in safe mode or safe mode w/command prompt. Holy Schmoly wrote in message ... Sorry, forgot to add that, from what I can observe, I think something is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message ... 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4ax .com... 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. |
#24
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Great, SC Tom. I'll give those things a try. At this point, I'm
willing to try anything. However, if even after these things I can't get NIC drivers to install properly, then do you think a clean reinstall of my XP Pro would resolve this issue, or do you think that this is more of a hardware related problem and a reinstall just might not fix this issue? Thanks. On Tue, 2 Jun 2009 23:02:14 -0400, "SC Tom" wrote: Well, I haven't done this in a long time, so I may not remember the steps entirely. We had a problem at my old job with network cards and connectivity, and IIRC, the fix was to remove TCP/IP and other protocols in network properties, reboot, then reinstall. Not sure if that would work here (probably not), but might be worth a try. Are you showing any errors in event viewer? Might be something there. It's puzzling to me that the drivers won't install. Do you have anything in add/remove programs left over from the old NIC? Have you tried updating your MB drivers? Not the NIC, but the chip set drivers. I'm wondering if maybe the MB was affected by the power flux. Have you tried using system restore to bring it back to a date before the problems started? You may have to do it in safe mode or safe mode w/command prompt. Holy Schmoly wrote in message .. . Sorry, forgot to add that, from what I can observe, I think something is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message m... 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 news8o825lr9ed273lbsd3k0oacjn388dnhba@4ax. com... 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4a x.com... 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. |
#25
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Great, SC Tom. I'll give those things a try. At this point, I'm
willing to try anything. However, if even after these things I can't get NIC drivers to install properly, then do you think a clean reinstall of my XP Pro would resolve this issue, or do you think that this is more of a hardware related problem and a reinstall just might not fix this issue? Thanks. On Tue, 2 Jun 2009 23:02:14 -0400, "SC Tom" wrote: Well, I haven't done this in a long time, so I may not remember the steps entirely. We had a problem at my old job with network cards and connectivity, and IIRC, the fix was to remove TCP/IP and other protocols in network properties, reboot, then reinstall. Not sure if that would work here (probably not), but might be worth a try. Are you showing any errors in event viewer? Might be something there. It's puzzling to me that the drivers won't install. Do you have anything in add/remove programs left over from the old NIC? Have you tried updating your MB drivers? Not the NIC, but the chip set drivers. I'm wondering if maybe the MB was affected by the power flux. Have you tried using system restore to bring it back to a date before the problems started? You may have to do it in safe mode or safe mode w/command prompt. Holy Schmoly wrote in message .. . Sorry, forgot to add that, from what I can observe, I think something is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message m... 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 news8o825lr9ed273lbsd3k0oacjn388dnhba@4ax. com... 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4a x.com... 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. |
#26
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
I'm truly stumped as to hardware or software at this point. If a Restore
doesn't work, maybe a repair installation of XP? Is there any way you could hook the PC up somewhere else, like a friends house, to their internet connection? If it doesn't work there, at least you'll know it's your machine and not the ethernet cable, modem, etc. Holy Schmoly wrote in message ... Great, SC Tom. I'll give those things a try. At this point, I'm willing to try anything. However, if even after these things I can't get NIC drivers to install properly, then do you think a clean reinstall of my XP Pro would resolve this issue, or do you think that this is more of a hardware related problem and a reinstall just might not fix this issue? Thanks. On Tue, 2 Jun 2009 23:02:14 -0400, "SC Tom" wrote: Well, I haven't done this in a long time, so I may not remember the steps entirely. We had a problem at my old job with network cards and connectivity, and IIRC, the fix was to remove TCP/IP and other protocols in network properties, reboot, then reinstall. Not sure if that would work here (probably not), but might be worth a try. Are you showing any errors in event viewer? Might be something there. It's puzzling to me that the drivers won't install. Do you have anything in add/remove programs left over from the old NIC? Have you tried updating your MB drivers? Not the NIC, but the chip set drivers. I'm wondering if maybe the MB was affected by the power flux. Have you tried using system restore to bring it back to a date before the problems started? You may have to do it in safe mode or safe mode w/command prompt. Holy Schmoly wrote in message . .. Sorry, forgot to add that, from what I can observe, I think something is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message om... 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 news8o825lr9ed273lbsd3k0oacjn388dnhba@4ax .com... 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4 ax.com... 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. |
#27
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
I'm truly stumped as to hardware or software at this point. If a Restore
doesn't work, maybe a repair installation of XP? Is there any way you could hook the PC up somewhere else, like a friends house, to their internet connection? If it doesn't work there, at least you'll know it's your machine and not the ethernet cable, modem, etc. Holy Schmoly wrote in message ... Great, SC Tom. I'll give those things a try. At this point, I'm willing to try anything. However, if even after these things I can't get NIC drivers to install properly, then do you think a clean reinstall of my XP Pro would resolve this issue, or do you think that this is more of a hardware related problem and a reinstall just might not fix this issue? Thanks. On Tue, 2 Jun 2009 23:02:14 -0400, "SC Tom" wrote: Well, I haven't done this in a long time, so I may not remember the steps entirely. We had a problem at my old job with network cards and connectivity, and IIRC, the fix was to remove TCP/IP and other protocols in network properties, reboot, then reinstall. Not sure if that would work here (probably not), but might be worth a try. Are you showing any errors in event viewer? Might be something there. It's puzzling to me that the drivers won't install. Do you have anything in add/remove programs left over from the old NIC? Have you tried updating your MB drivers? Not the NIC, but the chip set drivers. I'm wondering if maybe the MB was affected by the power flux. Have you tried using system restore to bring it back to a date before the problems started? You may have to do it in safe mode or safe mode w/command prompt. Holy Schmoly wrote in message . .. Sorry, forgot to add that, from what I can observe, I think something is preventing the drivers of both the onboard NIC and the new NIC from being installed properly for some reason. I had run a virus and malware scanner right away when I had problems with the onboard NIC and I ran it again just in case and nothing came up. Please help! On Tue, 02 Jun 2009 13:09:16 -0600, Holy Schmoly wrote: SC Tom, I went and bought a cheap new NIC, D-Link DFE-538TX, and followed the installation instructions carefully and when all was said and done, I still have the same problems. I had disabled the onboard NIC in the BIOS before installing the drivers for the new card and proceeded to follow the instructions that came with it. The instructions we (I had already disabled the onboard NIC at this point) Install the driver off the included CD (no error messages, so figured all was fine), turn off the PC, install the NIC in one of the PCI slots, turn on the PC. However, even the new NIC is showing the yellow exclamation mark in the Device Manager after I had turned the PC back on. So, I uninstalled the NIC in the Device Manager, rebooted and this time I manuall located the driver and the error message I got was that there was a problem installing the hardware and when I double click on the NIC in the Device Manager, it says that the drivers for this device are not installed (code 28). I'm really at a loss here, can you think of something that might be causing this problem with drivers not being installed properly? I am logged in as admin the whole time. Thanks for your time and courtesy. On Tue, 2 Jun 2009 07:23:21 -0400, "SC Tom" wrote: They're yellow now because there are no NIC drivers installed. Once the NIC and drivers are in place, the error with them should clear up. I hope it all works out. Let us know how it goes. (Keep your receipt just in case :-) ) SC Tom Holy Schmoly wrote in message om... 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 news8o825lr9ed273lbsd3k0oacjn388dnhba@4ax .com... 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 news:tad025p6l15a0608v47v4ecjqolkkbn0aq@4 ax.com... 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. |
#28
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
SC Tom, thanks for all the help you provided. I ended up just doing a
repair installation and now Windows is letting my onboard NIC function properly again. So, I guess it wasn't a hardware issue at all after all. For some reason, something was preventing the drivers for the NIC to install, let alone load. Just glad everything's back to normal. Thanks again. On Wed, 3 Jun 2009 06:54:08 -0400, "SC Tom" wrote: I'm truly stumped as to hardware or software at this point. If a Restore doesn't work, maybe a repair installation of XP? Is there any way you could hook the PC up somewhere else, like a friends house, to their internet connection? If it doesn't work there, at least you'll know it's your machine and not the ethernet cable, modem, etc. |
#29
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
SC Tom, thanks for all the help you provided. I ended up just doing a
repair installation and now Windows is letting my onboard NIC function properly again. So, I guess it wasn't a hardware issue at all after all. For some reason, something was preventing the drivers for the NIC to install, let alone load. Just glad everything's back to normal. Thanks again. On Wed, 3 Jun 2009 06:54:08 -0400, "SC Tom" wrote: I'm truly stumped as to hardware or software at this point. If a Restore doesn't work, maybe a repair installation of XP? Is there any way you could hook the PC up somewhere else, like a friends house, to their internet connection? If it doesn't work there, at least you'll know it's your machine and not the ethernet cable, modem, etc. |
#30
|
|||
|
|||
Is onboard NIC kaput? (ipconfig output: Unable to query host name.)
Sorry I couldn't be more help, but I'm glad it's all OK now. At least with
the repair installation, you didn't lose all your programs. SC Tom cartridge wrote in message ... SC Tom, thanks for all the help you provided. I ended up just doing a repair installation and now Windows is letting my onboard NIC function properly again. So, I guess it wasn't a hardware issue at all after all. For some reason, something was preventing the drivers for the NIC to install, let alone load. Just glad everything's back to normal. Thanks again. On Wed, 3 Jun 2009 06:54:08 -0400, "SC Tom" wrote: I'm truly stumped as to hardware or software at this point. If a Restore doesn't work, maybe a repair installation of XP? Is there any way you could hook the PC up somewhere else, like a friends house, to their internet connection? If it doesn't work there, at least you'll know it's your machine and not the ethernet cable, modem, etc. |
Thread Tools | |
Display Modes | |
|
|