IPV6toIPV4 Adapters Galore

[HammerHead]

Every time I boot a "IPV6toIpV4 adapter" is added in my device tree. Is IPv6 necessary at this time? What is wrong with my Marvell Lan controller that this happens? Am I missing some tweak?

 

[chev65]

I havn't a clue on why this happens but I think it's a driver problem of some sort. You can delate those extra adaptors by going into device manage go to view then choose "show hidden devices" delate them all and a new one will be made but it should not be making one everytime you reboot.

 

[HammerHead]

Drivers

Drivers are not the problem, Unless the latest driver is at fault also. I just installed Marvells latest (Ver 11.30.1.3 dated 9/15/2010). It maybe the driver anyhoo.

I deleted 73 adapters from the device tree. As I reboot they are begining to come back. Is some of the addressing we are using on the web now in the IPV6 format?

 

[chev65]

The IPv6 protocol is only used on the LAN with Windows 7 so it's not used to get to websites.

The Argument against Disabling IPv6
It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx

 

[WindowsStar]

The IPv6 protocol is only used on the LAN with Windows 7 so it's not used to get to websites.

The Argument against Disabling IPv6
It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx

Again +1

 

[chev65]

The IPv6 protocol is only used on the LAN with Windows 7 so it's not used to get to websites.

The Argument against Disabling IPv6
It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx

Again +1

LOL, seems like nobody knows what IPv6 is used for so I just keep posting up the relevant facts about it.

Although I havn't a clue on why the OP is having this problem I have seen this problem before but havn't found anything conclusive on how to fix it yet.

 

[HammerHead]

Suggestions?

I have two of these rigs. MoBo's are identical. One rig is not adding these "adapters". The driver for the Marvell Lans on that one is 11.22.3.9 9/28/2009. I am looking for the inf file with that driver. I think that driver came with the early versions of windows 7. (oeminf5? something on that order). Its a 32 bit driver but it is working well on my 64 bit machine. I can find references to the file doing searches but can't find a download.

I have those file and drivers on the other rig. If I can figure out how to find them. It will take a *.inf and one or two other files. If I can find the inf the files needed will be listed in it.

 

[chev65]

The Asus support site shows this for your LAN driver> Marvell Yukon Gigabit Ethernet Driver V11.10.5.3 for 32/64bit Windows 7.(WHQL)

There are also some very recent bios updates 9/10/2010 for your board at the Asus site.

ASUSTeK Computer Inc.-Support-

I can only hope that you don't have the dreaded bonjour service installed.

 

[HammerHead]

Asus Drivers

I have copies of the Asus drivers and my bios are up to date.

Bonjour Service? Is that anything like Adios MF?

 

[smschulz]

Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, Home Group in Windows 7 and Direct Access in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Of course if you are not using any of the fore-mentioned services then disabling can't really hurt anything either.

 

[HammerHead]

Home Net

I am using a home network. (two rigs) So I better let IPV6 alone. I just uninstalled the adapters and rebooted and let windows put in a driver. Win installed 11.27.1.3. dated 6/14/2010. I rebooted and didn't see any new adapters. Maybe I am out of the woods.

 

[chev65]

Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, Home Group in Windows 7 and Direct Access in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Of course if you are not using any of the fore-mentioned services then disabling can't really hurt anything either.

Yes it can hurt, you missed the entire point, disabling that service isn't an option and even if it did fix something it would only be masking an underlying problem.

 

[HammerHead]

Gone?

I have rebooted 3 times and do not see any new adapters being added. I may be premature but I am going to call it solved. That would mean it was a driver problem.

Lesson learned for the umpteenth time --- latest driver not always the best.

 

[chev65]

I have rebooted 3 times and do not see any new adapters being added. I may be premature but I am going to call it solved. That would mean it was a driver problem.

Lesson learned for the umpteenth time --- latest driver not always the best.

The one thing I was pretty sure of was that it is a driver problem because I have seen similar complaints and the only way to fix the problem was to find another driver.

Sometimes the default Win7 drivers work best other times you have to get them from the manufacture and it's hard to say which one will work best.

Anyway, I'm glad that changing drivers worked for you.