silkshadow
n00b
- Joined
- Aug 9, 2010
- Messages
- 58
This is an HTPC. Its older and not used much. Its in a guest room. I have relatives coming for the Christmas holidays so am running though and making sure all my house tech works. Its on a Asus A8N-SLI SE and was using the mobo NIC. While, as you will see, hardware is probably not relevant, I'd be happy to post the full specs if anyone thinks it might be relevant. Its running Win7 32bit.
Here's the scenario. I booted the PC up 2 weeks ago, it was working fine. Win update complained that it needed a ton of updates, so I let it run. Win update finished and I rebooted. My security app, Outpost security suite, nagged me that it needed an update. It was a major update from v6 to v7. I did the update and shut the PC off. I did not do a followup test unfortunately. These are the only things I changed.
Went back to it this weekend, doing a final run though my place to make sure all the guest rooms were operational. Booted this PC up and no network, the icon had a red 'X'. I checked device manager and the NIC was gone but there was this thing called Teredo which was giving me a error code 10. Did some google found out what teredo was.
This puzzled me, as I have IPv6 turned off (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters\) as well as unchecking IPv6 in the NIC properties. Anyway,
'netsh interface teredo set state disabled'
then rebooted. Teredo is now disabled but my NIC is still not there. So I uninstall Teredo and reboot. Now I have no NIC in device manager at all (teredo was considered a NIC by DevMan). Crud, so I reboot, disable the onboard NIC in bios and boot. Then reboot and enable the NIC in bios. NIC is back, yay. Turn off the PC.
Came back to it on Sunday to see if everything is still ok. Its not, boot up and no NIC. So I think may be its hardware. So I have a ton of PCI NICs so I swap one in. Install the driver and reboot, NIC is there and network is up. Turn off the PC. Turn it back on, no NICs again.
This goes on for a bit, I tested the NIC in another computer and ran the broadcom diagnostic app on it (that comes with the card), its working fine. I reinstalled teredo, enabled and disabled the mobo NIC, tried multiple NICs (dlink, huawei, zte) etc. Nothing is stable, the NICs will install and the network will be up then on reboot it will disappear. Uninstalling and reinstalling teredo has no effect. Its always errored when enabled (probably because I have disabled IPv6).
I am stumped! Does anyone have any ideas to try? Thank you for any assistance here!
Edit: See down the thread, seems Outpost is the problem.![Frown :( :(](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Here's the scenario. I booted the PC up 2 weeks ago, it was working fine. Win update complained that it needed a ton of updates, so I let it run. Win update finished and I rebooted. My security app, Outpost security suite, nagged me that it needed an update. It was a major update from v6 to v7. I did the update and shut the PC off. I did not do a followup test unfortunately. These are the only things I changed.
Went back to it this weekend, doing a final run though my place to make sure all the guest rooms were operational. Booted this PC up and no network, the icon had a red 'X'. I checked device manager and the NIC was gone but there was this thing called Teredo which was giving me a error code 10. Did some google found out what teredo was.
This puzzled me, as I have IPv6 turned off (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters\) as well as unchecking IPv6 in the NIC properties. Anyway,
'netsh interface teredo set state disabled'
then rebooted. Teredo is now disabled but my NIC is still not there. So I uninstall Teredo and reboot. Now I have no NIC in device manager at all (teredo was considered a NIC by DevMan). Crud, so I reboot, disable the onboard NIC in bios and boot. Then reboot and enable the NIC in bios. NIC is back, yay. Turn off the PC.
Came back to it on Sunday to see if everything is still ok. Its not, boot up and no NIC. So I think may be its hardware. So I have a ton of PCI NICs so I swap one in. Install the driver and reboot, NIC is there and network is up. Turn off the PC. Turn it back on, no NICs again.
This goes on for a bit, I tested the NIC in another computer and ran the broadcom diagnostic app on it (that comes with the card), its working fine. I reinstalled teredo, enabled and disabled the mobo NIC, tried multiple NICs (dlink, huawei, zte) etc. Nothing is stable, the NICs will install and the network will be up then on reboot it will disappear. Uninstalling and reinstalling teredo has no effect. Its always errored when enabled (probably because I have disabled IPv6).
I am stumped! Does anyone have any ideas to try? Thank you for any assistance here!
Edit: See down the thread, seems Outpost is the problem.
Last edited: