See - How do I uninstall the IPv6 porotcol? - in the following document:

 

http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

 

Steve

Which version of Windows are you running?

 

Steve

Hi,

 

Thanks for replying.

 

OS: XP Pro SP2 + all updates including this month's.

 

I should also have mentioned that I downloaded and installed the latest 1400 wireless driver from Dell for this sytem prior to noticing this error.

 

File name: R143355.EXE

 

PS: Release date is Feb 2007 but file name is the same as an older one I downloaded some time ago (maybe last year).

 

I did not check after the latest version has been installed (only verified wireless connection is good) and it is the one currently installed in the system.

 

Thanks.

Hi,

 

Thanks.

 

Maybe I did not make myself clear.

 

I do know how to uninstall and re-install TCP/IP version 6 using methods in the article (and thanks for the link for which I also read some other info).

 

I do not know, however, how to install or add the protocol without having the same error indicated in the subject - Microsoft Tun Miniport Adapter.

 

Thanks and appreciate if anyone know how.

Is there a reason that need to have the IPv6 protocol installed on your computer?

 

Steve

Hi,

 

The short answer is: I don't know.   The long answer is: I am trying to solve the conflict error and found out it may have something to with TCP/IP version 6.  I don't know when and how version 6 had been installed.  According to information from MS, it may have been installed along with SP2.  In any case, it is not version 6 that I am interested to solve, it is the conflict that I wish to solve.  Thanks. 

Vista?

 

It's more like committing a suicide for solving a minor problem in life. Well, thanks.  I think that I will move on for now and take my chances.  Thanks anyway.

I seriously doubt that you need or want IPV6.  In fact IPV6 is causing problems.  My solution would be to get rid of it. Once it is gone the problem goes away because there is not conflict.  If that is not what you want to hear, then start a new thread and I will stay out of the discussion. 

 

Steve

Hi,

 

No offense, and I appreciate your response.  However, this thread as it indicated is about how to solve the conflict.  I don't think that I need to start a new thread.  I did not ask about how to solve version 6 problem.  Again, I have no idea and preference in terms of having version 6 or not.  I did not install it on my own (as least, not I know).  If it is already installed and I removed it so I don't see the conflict; it is not solving the problem but "avoding" the problem.  I could do that and that is what I have done.  But I am here to know if there are any solution instead of running away from the problem.

 

Thanks as always.

Yes, there is a solution - get Windows Vista which is designed to work with IPV6.  I have yet to see any need for an XP computer to use IPV6.  Of course Vista comes with another set of unsolved problems from Microsoft.  The reason I said to start a new thread is that many users just look through the forums quickly and skip threads where it looks like the question is being addressed.  So long as I keep answering, your problem may get ignored.  Since I won't answer if you start a new thread, you may find some help.

 

Steve

:smileyhappy: Solved - :smileyvery-happy:

 

Ok, hope the following will help those who might run into the same problem.

(1) Cause: Exact cause is unknown, maybe is caused by corrupted registry
files due to remove and re-install applications.

(2) Symptom: Yellow exclamation mark for Microsoft Tun Miniport Adaptor #2
in Device Manager.

(3) Short-term solution: Removing TCP/IP version 6 may also remove the
adapter, and thus the conflict.  But this is not a "solution" per se.

(4) Long-term solution as follows:

Thanks for the tips and discussion in here: http://www.testmy.net/topic-2373
by Bazza25  who mentioned related driver info: (tunmp.sys
c:\windows\system32\drivers
netip6.pnf c:\windows\inf
nettun.pnf c:\windows\inf)

Note: My solution involves "delete" registry files so use it at your own
risk.

Step 1: Remove TCP/IP version 6 protocol and reboot.

Step 2: In Normal mode, move tunmp.sys from its current location and another
location.

Step 3: Boot into Safe Mode (without Network)

Step 4: Run "Regedit" and search for every reference to Microsoft Tun
Miniport Adaptor and delete them (backup first)  Note: You may also find
some entries in ControlSet2, ControlSet3... and you may not delete some of
them, but it's ok.  The most important thing is to delete those entries in
the current controlset.

Step 5: Go to Device Manager and remove Microsoft Tun Miniport Adaptor
(Note: If you did not delete registry entries and did not move tunmp.sys to
another location, you can not remove this adapter as it will be preloaded).

Step 6: Boot to Normal Mode

Step 7: See if you have other conflicts and all other Network adapters have
been properly recognized.

Step 8: If so, Move tunmp.sys back to its original location.  Note: Just for
precautious, turn off your AV and Firewall and disconnect from the net.

Step 9: Now you can add TCP/IP version 6 protocol back without any error.

Additional notes:

I guess the issue is that, unlike other network adapters, Microsoft Tun
Miniport Adaptor can only have one entry and cannot have #2, #3, and so on,
or otherwise, it will mess up the driver version even using both are
pointing to the same file - tunmp.sys.  I also noticed that at one time,
Adapter #2 did not have conflict but it was the first Microsoft Tun Miniport
Adaptor that had the yellow exclaim mark.  So based on those, I decided to
take a more drastic approach to delete all registry entries and to "cheat"
Windows that there is none in the system.  So when I added back TCP/IP
version 6 (which will automatically created this adapter entry), it will not
have #2 but only one.

Hope this helps.