Hello AllIPv6 protocol installed by Windows 7 beta to network adaptor, can cause some problems with network connectivity if is used router that does not support IPv6 or have problems working if IPv6 protocol is enabled.You can disable IPv6 protocol to escape from these problems, but you must know, that disabling IPv6 protocol on windows 7 beta, prevents you from creating of home groups.If you leave home group for some reason and then you want to create new home group but IPv6 protocol is disabled, windows give you some message that says you need to set you network type to Home Network in order to create Home Group, and creation process of New Home Group breaks on this point.When you open Network and Sharing Center to set your network type to Home Network, you see that it is already set to Home Network.So if you want to create new Home Group you must open Network Adapter properties and to re enable IPv6 support.After IPv6 support is enabled you will be able to create new Home Group.After ctreation processof home group finish you can dissable IPv6 support again, but you must know that thismay brigs to you new unexpected problems like that I described here.Windows 7 troubleshooter tool, detects that you are not loged in home group, but cannot fix it

Bump :)I hope MS developers to see this and to fix it ASAP :)

Although itis common practice for "experts" to recommend disabling IPv6 in Vista and now Windows 7 I find that in very few cases does IPv6 cause problems. The problems with older networking hardware are usually caused by other features like TCP Auto-tuning, Receive-Side Scaling, and TCP Offload. If you have a problem with some old hardware I recommend leaving IPv6 enabled and try various settings for the other features. Usually this will fix the problem. I only try disabling IPv6 when the changing the other settings doesn't work. So far I have not found one case where disabling IPv6 on it's own fixed anything.Kerry Brown MS-MVP - Windows Desktop Experience

There is an article in Germany's c't computer magazine describing the new networking implementation in Windows 7. MS uses a new method for name resolving, called "Peer Name Resolution Protocol" (PNRP). PNRP is based on IPv6 and HomeGroups are based on PNRP. If you disable IPv6, you will loose HomeGroups, as Mr. Alexandriyski already mentioned. So there will be no fix for this. "It's not a bug, it's by design" Windows 7 x64 - Gigabyte EP-45-DS3 (Intel P45 chip set), 4GB RAM, ATI 4670

Hi, i have installed my win7 RC prefering homegroup and now i not browse my share on w2k PC .... including in group HOMEGROUP Do you know if with WORKGROUP exist the same problem and if possible switch from homegroup2workgroup. Thanks you

There is an article in Germany's c't computer magazine describing the new networking implementation in Windows 7. MS uses a new method for name resolving, called "Peer Name Resolution Protocol" (PNRP). PNRP is based on IPv6 and HomeGroups are based on PNRP. If you disable IPv6, you will loose HomeGroups, as Mr. Alexandriyski already mentioned. So there will be no fix for this. "It's not a bug, it's by design" Windows 7 x64 - Gigabyte EP-45-DS3 (Intel P45 chip set), 4GB RAM, ATI 4670 When we experimented disabling ipv6 on PCs a few issues immediately jumped out.We run cached credentials in our environment, just an fyi.1. Any time a standard user attempted to log on to a Windows 7 machine for the first time, it would hang and freeze while creating a profile causing a need to force a reboot. After a reboot the standard user could log on. Domain Admins had no issues creating a profile on a machine.2. 5 out of every 10 log on attempts (after profile creation) would result in the user not getting group policy, logon script, homeshare, drives, etc..., but could go to websites and do anything else one would be able to do on a laptop outside the work environment.edit: we are ipv4 environment.

Although it is common practice for "experts" to recommend disabling IPv6 in Vista and now Windows 7 I find that in very few cases does IPv6 cause problems. The problems with older networking hardware are usually caused by other features like TCP Auto-tuning, Receive-Side Scaling, and TCP Offload. If you have a problem with some old hardware I recommend leaving IPv6 enabled and try various settings for the other features. Usually this will fix the problem. I only try disabling IPv6 when the changing the other settings doesn't work. So far I have not found one case where disabling IPv6 on it's own fixed anything. Kerry Brown MS-MVP - Windows Desktop Experience And then there are those cases where "experts" discover that a network bottleneck suddenly clears up when IPv6 is disabled on that box, or the Windows 7 PC is turned off...in the state of rebooting...or something where the network services of that machine are not running. Which leads to a conclusion that the IPv6 services are the direct cause especially when the network is literally only affected when that computer is turned on *with IPv6 running*. Cases like this are usually in larger environments when there are multiple layers of IT services such as at a university. Usually something upstream has network policies that restrict something too much or whatever. This can't be helped in these cases and must be worked around. Then there's also those who attack the IPv6 protocol services because they're currently not watched as closely as IPv4 because people don't yet think about IPv6 when they think about locking things down. As a result IPv6 has some wide open services or unpatched exploits that in my experience have allowed some people to gain entry to systems where both admins and home users felt that they were completely locked down. Woops, didn't disable IPv6 or firewall it. The thought is "well nobody uses it yet". It may just be my *nix mentality disabling *network* services that aren't (and in most cases will never be) used on a particular computer, but that's what I've always done. Now yes on a home system where there's nothing complex or critical going on and IPv6 is turned off at the gateway for incoming traffic it's perfectly fine. In fact it's served as a nice backup to break into headless boxes when IPv4 services had issues and I wasn't in a position to reboot the box (away from home, whatever). But that same 'other way in' is exactly how some systems get compromised easily. IPv6 can be more trouble than one might think when it comes to security. Edit: on another note what a weird way of "deleting" posts this forum has.

I don't disagree that as IPv6 is relatively new, not well understood by most, and that there are security implications. On a large network if you want to block IPv6 you should be able to do this at the switch level. Trying to ensure that all the clients aren't using it is next to impossible. Blocking it on the network shouldn't affect the Windows clients unless you're using Windows 2008 R2 servers, Exchange 2007, etc.. Disabling it on the Windows clients can cause problems if it's not done properly (i.e. via a regedit).In the context of this thread users should be using a public network profile if connected to a University network so Homegroups wouldn't work anyway. In a large business network they'd be using a domain or work network profile so again Homegroups would be disabled.Kerry Brown MS-MVP - Windows Desktop Experience

What MANY people do not get is Homegroup is for HOME just as HOME versions of windows are not for business class networking. Disabling IP6 has cleared up many issues, and yes the folks could have just gone out and purchased supported gear, but getting some companies to part with MORE cash these days is getting harder and harder.I like the other poster like to kill anything not needed (like IP 6 on networks which do not support it).I got called out ona network issue..the corp A/V would not load..why they purchased HOME versions of windows 7 . No support for home versions..they of coursed wanted to blame microsoft for having to many versions of windows.Some folks.....