I hate to post something that has so much material associated but 18 hours of wading through the muck has not gotten my problem solved. I have a desktop and a laptop. Desktop runs Win 7 x64 Pro SP1 and laptop is Win 7 Ultimate x64 w/ SP1 installed. Homegroup can be created by either PC but then the other can't join. Same error on both - Unexpected error and "This computer cannot join a homegroup". I have so far: synced clocks added a registry entry for disabled components as there was not one, and set value = 0 (dword 32 bit only) reset ipv6 stack disabled and reenabled ipv6 checked the 8 services that are mentioned in every homegroup forum post disabled firewall on both machines and uninstalled security essentials. It has worked before with a different laptop running same version of Windows 7 ultimate. I think it is related to ipV6 because I can ping localhost with ipv6 but no farther. ipv4 works fine any direction. With ipv6 I can't even get a return packet from my default gw which is a Belkin 300 Share+ router F7D3301 v1. Host name resolution is working but pings won't come back if ipV6. If it is a router / switch issue which is what it is looking like to me, then why all of a sudden it doesn't work when it used to? For something that was supposed to make it easy, it sure is complicated. I've had no problems with work groups, just homegroup.

have you considered the logon /password for each machine. -- mikeyshd "Anthony Kaz" wrote in message news:e36e7c38-f9ee-40ef-9b63-26f5555a0ff3@communitybridge.codeplex.com... > I hate to post something that has so much material associated but 18 hours > of wading through the muck has not gotten my problem solved. I have a > desktop and a laptop. Desktop runs Win 7 x64 Pro SP1 and laptop is Win 7 > Ultimate x64 w/ SP1 installed. Homegroup can be created by either PC but > then the other can't join. Same error on both - Unexpected error and "This > computer cannot join a homegroup". I have so far: > > synced clocks > > added a registry entry for disabled components as there was not one, and > set value = 0 (dword 32 bit only) > > reset ipv6 stack > > disabled and reenabled ipv6 > > checked the 8 services that are mentioned in every homegroup forum post > > disabled firewall on both machines and uninstalled security essentials. > > It has worked before with a different laptop running same version of > Windows 7 ultimate. > > I think it is related to ipV6 because I can ping localhost with ipv6 but > no farther. ipv4 works fine any direction. With ipv6 I can't even get a > return packet from my default gw which is a Belkin 300 Share+ router > F7D3301 v1. Host name resolution is working but pings won't come back if > ipV6. If it is a router / switch issue which is what it is looking like to > me, then why all of a sudden it doesn't work when it used to? > > > > For something that was supposed to make it easy, it sure is complicated. > I've had no problems with work groups, just homegroup. >

Mickeyhsd, Thankyou for at least posting something. I guess there are not a lot of people with answers for ipv6 and homegroup problems. I apologize for taking so long to get back here. i kind of thought I's get an email or something if there was a response. i will check back more frequently now. As to your question, I'm not sure what you mean so I'd have to say, no? Machines both use the same logon and password. Would a particular combination cause the association to fail?

Anyone? Bueller? Anyone?

So is this why people get mad at Microsoft? This post has been up for how long and the best response is "have you considered the logon /password for each machine"? Really? No offense to mikeyhsd but i would have hoped i could get someone with a couple fancy letters near their name to take a look at it see if they can't find something I'm doing or not doing to make this not work. Heck at least blame it on my router.