Terredo Tunneling, etc.

[Guest]

What in the heck is that? I was checking Device Manager yesterday and found
that there was an Exclamation mark in the yellow triangle next to: "Teredo
Tunneling Pseudo-Interface" and it's listed under Network Adapters. I
tried to update drivers, but it kept telling me the one installed were the
best available. What is it and do I need it? It wasn't there before because
I went to the device manager to check on my video drivers and there was no
yellow triangle there then. That was 3 or 4 days ago.

There's also a yellow triangle next to "USB CF Reader" Have no idea where
that came from and it wasn't there the other day either.

Both state the following: "Windows cannot start this hardware device
because its configuration information (in the registry) is incomplete or
damaged. (Code 19)

Click 'Check for solutions' to send data about this device to Microsoft and
to see if there is a solution available."

I've click the "Check for solutions", but nothing happens.

Any suggestions? Thanks in advance.

 

[LaRoux]

Since you didn't get any responses, I thought I would take a shot.

Rather than pretend that I know much more about this than that it's a
protocol used for IPv6 to IPv4 traffic, here's an overview incase you are
interested in the details:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspx

Especially note the following "In Windows Vista, the Teredo component is
enabled but inactive by default. In order to become active, a user must
either install an application that needs to use Teredo, or configure
advanced Windows Firewall filter settings to allow edge traversal"

If none of this sounds familiar, do you have some sort of VPN software that
has been installed?

 

[Guest]

HUH???? Well, that was as clear as mud. LOL but thanks for the info.

I don't have any VPN software installed and I don't have a network. This is
a stand-alone computer and I'm the only user. So I don't know if I should
just ignore it or uninstall it or what? Talk about confusing. I mean the
system seems to be working fine, it's just that I don't like the yellow
triangles. Call me paranoid. LOL

 

[LaRoux]

You are accessing the internet and this news group presumably via a network
connection.

If it's dial-up, try disabling your network card (assuming you have one) and
this may make the exclamation point go away.

If it's broadband, I suppose it's possible that you have some sort of
software provided by your ISP that could be causing the problem.

 

[Guest]

Well, no, no software from my ISP either. I guess I'll just leave it alone.
If it ain't broke I guess I won't fix it. LOL

Thanks for your help.

 

[Harry Sherman]

I have had similar problems (yellow exclamation point in DM) with ISATAP and
6TO4.
These programs are related to Terredo, Tunnel, and the IPv4-IPv6
translation process.
Attempts to reinstall the drivers are unsuccessful with the same result you
got. If I delete them, they are simply recreated on next boot with same
error in DM. Disabling them does stick, and appears to have no effect on my
dialup connection, so I have decided to live with it. The problems first
surfaced last summer about two months after installation of Beta-1 and
continued in RTM (5600). If you are interested, MS has a KB article on the
problem with ISATAP that says despite the error shown in DM, the program is
working fine, and to ignore the error. I would assume that the same advice
is probably true with 6TO4 and Terredo.

 

[Guest]

Wow, thanks for your input Harry. Yes, like you I've sort of decided to just
live with it. Supposedly it sent a message to Microsoft about the problem,
so hopefully one day it will be resolved. Like you, I get paranoid when I
see those yellow triangles that just won't go away. LOL

Have a great day.

 

[CZ]

I have had similar problems (yellow exclamation point in DM) with ISATAP6TO4.
These programs are related to Terredo, Tunnel, and the IPv4-IPv6
translation process.
Attempts to reinstall the drivers are unsuccessful with the same result you
got. If I delete them, they are simply recreated on next boot with same
error in DM. Disabling them does stick, and appears to have no effect on my
dialup connection, so I have decided to live with it. The problems first
surfaced last summer about two months after installation of Beta-1 and
continued in RTM (5600). If you are interested, MS has a KB article on the
problem with ISATAP that says despite the error shown in DM, the program is
working fine, and to ignore the error. I would assume that the same advice
is probably true with 6TO4 and Terredo.

Harry:

I disabled IPv6 via the registry and Teredo and isatap were disabled per
ipconfig /all command.

Use regedit to access:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters\

Create new dword: DisabledComponents
Set dword value to: ff (in hex)

Reboot

Per following URL this will "Disable IPv6 over all interfaces and prefer
IPv4 to IPv6":

http://www.microsoft.com/technet/community/columns/cableguy/cg1005.mspx

 

[Guest]

DITTO: I have an XPC Barebones SD37P2 with Broadcom Netlink Gigabit Ethernet
and Teredo Tunneling Pseudo Interface installed. During a recent Vista update
the driver (or registry) has become corrupted [MESSAGE: Windows cannot start
this hardware device because its configuration information (in the registry)
is incomplete or damaged. (Code 19)]. Microsoft Vista could not find an
online solution, saying that the driver, Microsoft Tun Miniport Adapter, is
up to date. A volume error check did not resolve the problem. Please advise.
(Am experiencing same problem with cdrom.sys driver, and there, the problem
is serious, as I am not able to access furhter installation via CD/DVD!)