Quantcast
Channel: Microsoft forum - dslreports.com
Viewing all articles
Browse latest Browse all 8524

[WIN7] Microsoft ISATAP Adapter & Teredo Tunneling Pseudo Interface

$
0
0
Both "adapters" run on system32\tunnel.sys 1.) My DSL adapter and Internet connection are A-OK fine! 2.) Yes, I've been tinkering on brand new install of Windows 7 SP1 3.) I effectively disabled IPv6 function including nontunnel and tunnel interfaces 4.) I set start value for IPHELPER service to "Manual" 5.) I set start value for (perhaps unrelated?) TCP/IP NetBIOS Helper to "Manual" 6.) No related error, warning in Event Viewer...zip, nada! 7.) And just for the heck of it, I'll mention that I do have ZoneAlarm 2014 Free installed! VPN protocols disabled in ZoneAlarm...fyi Just noticed in Device Manager that two adapters (see title head) which apparently were hidden before now show with YELLOW exclamation mark. The notice is: "This device cannot start. (Code 10)" As stated above both run on "tunnel.sys" Because this popped up just about the time of my tinkering, I'm sure I caused this to show up. Now since I don't currently have IPv6 deployed on this standalone system I don't really care myself about the "tunnel.sys" driver. For the moment, I simply disabled both adapters until I could get more info. Should I care about this for the time being? I've read in the Vista days MS said that the YELLOW exclamation mark on these two items could be ignored. Probably not the same for Windows 7? I've read some suggest UNINSTALLING both adapters and rebooting to let Windows automatically reinstall. But if one of my IPv6 tweaks is causing "tunnel.sys" not to run (perhaps because of a service that's not starting, or who knows what???) won't these adapters just show up again with CODE 10? Once again...neither my overall system or my Internet connection (including WiFi) are affected in the least by this issue.

Viewing all articles
Browse latest Browse all 8524

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>