So, i'm discovering certain features of Windows 7 in a ipv4 environment requires various components of ipv6. My current employers require me to completely disable ipv6. I would love to see some documentation describing the features used, or can someone explain what features are used and what features are not needed?-thanks

UP v6 is now being rolled out widely. Some old equipment may need to be updated. There is a shortage of IP v4 and while NAT has helped there is now few IP 4 addresses left for ISPs to add more users with.IT/Developer, Windows/Linux/Whatever I need a new web server, the antique IBM 300GL has a 137GB disk limit, for my chess site. I wanted to post many more downloadable files, the existing 30GB disk is insufficient.

Thank you for the reply, however this has nothing to do with my question.I am asking what parts of ipv6 does a Windows 7 machine use in a ipv4 environment?Example: DirectAccess uses a portion of ipv6 encryption over a ipv4 network.

The protocols are interleaved, you can use DHCP and it will work fine. IF you need static addresses, then there is a problem as forcing the IP v4 to static seems to not work properly.IT/Developer, Windows/Linux/Whatever I need a new web server, the antique IBM 300GL has a 137GB disk limit, for my chess site. I wanted to post many more downloadable files, the existing 30GB disk is insufficient.

Again, thank you for the reply. It still does not address my question. Let me clarify a bit.Which components of ipv6 does a Windows 7 PC use running dhcp on a ipv4 network?Which partsare essential and which parts can I disable safely?When I completely disable ipv6 in the registry, about 2 out of 5 logon attempts to the ipv4 domain fail... no group policy, no logon scripts run, no drives, no homeshare drive.When I leave tcpipv6 enabled, there are no issues logging on the ipv4 domain.Which components of ipv6 is the PC using to ensure a successful logon?

Flayofish, I understand your dilemma. Unfortunately, I dont have a direct answer to your question, but this TechNet article may lead you in the right direction. http://technet.microsoft.com/en-us/network/bb530961.aspx

Thanks Darien,I'll look through them and see if anything comes out of it.Meantime, if any of you other fellow forum browsers/professionals/enthusiasts/ninjas/pirates/etc... have any ideas, please share them.-thanks

Disabling IPv6 should have no affect when using a native IPv4 domain environment network. GP will work, you will be able to join domains, logon scripts will run, drives will map. If they are not for you I'm interested in hearing more about it. How exactly are you disabling ipv6, I'd like to reproduce this if possible.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

I have tried using static addresses, Windows 7 does not like that at all. Hard to manage when the infrastructure is old and not very smart.IT/Developer, Windows/Linux/Whatever I need a new web server, the antique IBM 300GL has a 137GB disk limit, for my chess site. I wanted to post many more downloadable files, the existing 30GB disk is insufficient.

Disabling IPv6 should have no affect when using a native IPv4 domain environment network. GP will work, you will be able to join domains, logon scripts will run, drives will map. If they are not for you I'm interested in hearing more about it. How exactly are you disabling ipv6, I'd like to reproduce this if possible. Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team I would think that it doesn't have an effect, but apparantly it does.When I disable tcp/ipv6 any non-domain admin that logs onto a pc for the first time hangs on "personalizing your desktop". you have to force a shutdown and reboot. Then he/she is able to logon normally. Even then, about 2 out of every 5 logon attempts ends in no GP, Network Drives, Logon Scripts, Homeshare Drive.I should point out that i am also required to remove "Link-Layer Topology Discovery Mapper I/O Driver" and "Link-Layer Topology Discovery Responder", but from what I have read these would have no bearing, or effect on this issue.I use regedit to disable ipv6 for all users.start-->run-->regeditNavigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\PerametersCreate a new 32bit Dword (this works for both x86 and x64 machines) and call it "DisabledComponents"Right-click and select modify. Fill in the field with all f's.Reboot.When you look at the properties of your network connection in "Network and Sharing Center" tcp/ipv6 will still show up with a check mark looking like its working, but it's not.You can verify by opening a command prompt as administrator and typing "ipconfig/all" you will see there are no longer any tcp/ipv6 entries.

I use regedit to disable ipv6 for all users. start-->run-->regeditNavigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\PerametersCreate a new 32bit Dword (this works for both x86 and x64 machines) and call it "DisabledComponents"Right-click and select modify. Fill in the field with all f's.Reboot.When you look at the properties of your network connection in "Network and Sharing Center" tcp/ipv6 will still show up with a check mark looking like its working, but it's not.You can verify by opening a command prompt as administrator and typing "ipconfig /all" you will see there are no longer any tcp/ipv6 entries. Flayofish, Why would you need to go into the registry to disable IPv6, when you can just as easily, and more safely, do it from the adapters properties box?

I setup a repro on build 7000 and a daily build in a domain and was unable to reproduce the issues you described, flayofish. After some general testing I also wrotea script that refreshed policy 100 times on each client and never saw your problem either. I suspect this is something specific to your environment, can you get network captures reproducing the issue, save NFO files from MSINFO32, and share them somewhere? Just so anyone reading this is clear - the only way to turn off IPv6 (mostly - there is NO WAY to fully turn off IPv6; try pinging ::1 after disabling if you do not believe me) is through the registry value described by flayofish and documented in KB929852. Despite what you will see in the NCPA.CPL UI checkbox being on or off, it is only (mostly) disabled with the disabledcomponents registry value. Unchecking it in NCPA.CPL does not disable IPv6. However, we do not recommend you turn IPv6 off. This will break Meeting Spaces, Remote Assistance, Homegroups, and DirectAccess. It may end up breaking other things as the Product Group does not rigorously test Win7 with IPv6 turned off, so most of our caught bugs with it come from dogfood and private beta customer testing. IPv6 is the future folks. Rather than hiding from the inevitable, start using it and get a leg up on the folks you are competing with in the workforce. A few years from now it will be everywhere and most folks that stuck with IPv4 knowledge will be seeing their jobs go to those who paid attention. If you don't believe me, go chat with all the IPX, SPX, NetBEUI, Token Ring, and ArcNet experts. Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Interesting. I learn something new everyday. I always keep IPv6 on; with this new knowledge about how IPv6 is not integrated into some of the inner workings of the OS, I will continue to do so.Thanks Ned.

There's also an IP Helper service in services.msc that "Provides automatic IPv6 connectivity over an IPv4 network. This service includes Teredo, ISATAP, 6to4 and Port Proxy functionalities. If this service is stopped, the machine will only have IPv6 connectivity if it is connected to a native IPv6 network."- John

I use regedit to disable ipv6 for all users. start-->run-->regeditNavigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\PerametersCreate a new 32bit Dword (this works for both x86 and x64 machines) and call it "DisabledComponents"Right-click and select modify. Fill in the field with all f's.Reboot.When you look at the properties of your network connection in "Network and Sharing Center" tcp/ipv6 will still show up with a check mark looking like its working, but it's not.You can verify by opening a command prompt as administrator and typing "ipconfig /all" you will see there are no longer any tcp/ipv6 entries. Flayofish, Why would you need to go into the registry to disable IPv6, when you can just as easily, and more safely, do it from the adapters properties box? I use the registry entry so I can disable it for all users. This also works for capturing and deploying a custom image. If i simply uncheck it, a deployed custom image will enable it.

I setup a repro on build 7000 and a daily build in a domain and was unable to reproduce the issues you described, flayofish. After some general testing I also wrotea script that refreshed policy 100 times on each client and never saw your problem either. I suspect this is something specific to your environment, can you get network captures reproducing the issue, save NFO files from MSINFO32, and share them somewhere? Just so anyone reading this is clear - the only way to turn off IPv6 (mostly - there is NO WAY to fully turn off IPv6; try pinging ::1 after disabling if you do not believe me) is through the registry value described by flayofish and documented in KB929852. Despite what you will see in the NCPA.CPL UI checkbox being on or off, it is only (mostly) disabled with the disabledcomponents registry value. Unchecking it in NCPA.CPL does not disable IPv6. However, we do not recommend you turn IPv6 off. This will break Meeting Spaces, Remote Assistance, Homegroups, and DirectAccess. It may end up breaking other things as the Product Group does not rigorously test Win7 with IPv6 turned off, so most of our caught bugs with it come from dogfood and private beta customer testing. IPv6 is the future folks. Rather than hiding from the inevitable, start using it and get a leg up on the folks you are competing with in the workforce. A few years from now it will be everywhere and most folks that stuck with IPv4 knowledge will be seeing their jobs go to those who paid attention. If you don't believe me, go chat with all the IPX, SPX, NetBEUI, Token Ring, and ArcNet experts. Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team Thank you for your reply.I am in the process of isolating what causes networking issues when certain aspects are disabled, so I can take this information to my managers and justify why it should remain enabled. Currently, the settings required by my employers are causing me "Beta Nightmares", so please keep the information coming.I'm setting up a testbed, this week, and deploying Win 7 x64 to several PCs to test various component combinations that will be disabled/enabled to try and narrow the issue down.edit: From what I have read on TechNet and from these forums, I totally agree with you on keeping IPv6 turned on. I was able to convence my managers to leave it enabled after showing them all the logon / first time logon issues resovled by doing so. Ned, are there any additional url's or documents you can point me to so I may further support this?My biggest battle will come with our Networking team. They are dead set against IPv6 and are firm against leaving ipv6 turned on the PCs despite the fact they do not need to update the network to ipv6. I could really use some hard documentation to back this up, so they will be comfortable with this.-thanks

There's also an IP Helper service in services.msc that "Provides automatic IPv6 connectivity over an IPv4 network. This service includes Teredo, ISATAP, 6to4 and Port Proxy functionalities. If this service is stopped, the machine will only have IPv6 connectivity if it is connected to a native IPv6 network." - John Thank you for the information, John.Would "Link-Layer Topology Discovery Mapper I/O Driver", or "Link-Layer Topology Discovery Responder" play a factor in my current issue?Currently required to disable all features except for: "Client for Microsoft Networks" and "Internet Protocol Version 4 (TCP/IPv4)".-thanks

I'll see what I can scrounge up - Win7 docs are going to be thin until we release. You might try a reverse tack with the Networking team and have them find MS documentation that advises people to turn it off in Win7. :)Ifthey have a Premier contract (I would hope so if they actually have a separate staff for networking) then they can open an Advisory case with us when the product releases and one of our 3rd tier SEE's can tell them more as well as send along internal info that we haven't yet published. The infoI gave was paraphrased from the lead Program Manager and Lead Developer of IPv6 at Microsoft.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Thank you for taking the time to look into this.

Hi, im little bit confused into this hole new area, i got recommended that i should tunr off my IPv6, hence i got a problem whit my "ms" when i upgraded to win 7. by turnig IPv6 off helps med a little bit to get my ms down to60during the game online but throughthe cmd --> ping www.google.se = ~60 ms videlicet higher when IPv6 was on and during the game online it was on >150 mswhen i had xp the "ms" was below 30 everywhere... ;D Now im readin that IPv6 should be on in someway...Yet so far i havent any problems whit my network but the "ms"is stil to high!I like win 7 very much, its a great system , but if there is no solve on the "ms" then im afraid i have to go back to xp.