I have three computers running Windows 7 (one desktop Dell 32 bit wired RC, one Toshiba laptop running 32-bit RC and a Gateway desktop 64-bit running RTM and wireless through Netgear card). All of them are connected to Verixon Fios router. My problem is I can't get the 64-bit system to connect to the Homegroup, the others no problem. I've tried changing the firewall setting, I even turned it off. I've even gone as far as buying an ethernet cable thinking it was the wireless connection, but still no connection. I thought when I updated the 64-bit system from the RC to the RTM it would fix it but it didn't. I've tried creating a Homegroup through the 64-bit system but the other computers won't connect to it.When I first started the process of trying to connect it, I would get the IPv6 error saying it wasn't activated, but that wasn't the case. Is it that the router isn't allowing the packets to transfers through IPv6? How do I fix this?Help!!

Try it without HomeGroup. That's the only way I could get my two systems to 'see' each other and an external drive.System #1 has XP Pro w/SP3, XP Pro x64 w/SP2, Win7 32-bit, and Win7 64-bit.System #2 has XP Pro w/SP3 and Win7 32-bit.The external drive is connected to the router to which both systems and the cable modem are connected.I had no problems at all getting any XP Pro system to 'see' any other XP Pro system or the external. Problems occured with Win7 both 32- and 64-bit installs.Had to finally remove Win7 systems from HomeGroup and turn off the two HomeGroups services. So far, everybody 'sees' everybody. I expect to have to do the same next month when final/upgrade is released.

Hi, Please understand that IPv6 was a core technology for HomeGroup and it depended on the RNRP service. This issue can occur if RNRP service was stopped or corrupted. Let's use the following steps to troubleshoot the issue. 1. Temporarily disable Firewall and third party antivirus program on the computer for a test. 2. Verify relevant services ========================= a. Click "Start", type "services.msc" (without quotation marks) in Search Bar and press Enter. Note: If you are prompted for an administrator password or confirmation, type your password, or click Continue. b. Right click the "Peer Networking Grouping" service and choose Properties. c. Please check if the service is started; if not, please click the Start button and see if it works. d. You may also choose Automatic next to Startup type. e. Click OK. f. Please repeat the above steps with another service: PNRP Machine Name Publication Service. 3. Modify IPv6 registry key to enable IPV6 ========================== a. Click Start, type regedit in Search Bar, and then click regedit in the Programs list. Note: If you are prompted for an administrator password or confirmation, type your password or click Continue. b. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters c. Check whether the "DisabledComponents" registry key exists. If so, let's move on the next steps. d. Double click the "DisabledComponents" registry key and modify the value to 0. (If the key doesn't exist, please create the key above and assign the value 0) e. Exit Registry Editor, and then restart the computer. For more information, we can refer to the link below: How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vista, Windows 7 and Windows Server 2008 Thanks, Novak

Greetings...Do you mean, add a 'string value' in the Parameters subkey? DisabledComponents does not exist...Also, PNRP brings the following error when trying to start...0x80630801: 0x80630801I'm guessing something isnot right here...Looking forward to your reply...EdFeed the Shark...

After countless hours of technical support, the following solution worked for me: Delete 'idstore.sst' from "C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking" Start the HomeGroup troubleshooter. PNRP service recreates the idstore.sst on restart. Hope this helps, Matt

After countless hours of technical support, the following solution worked for me: Delete 'idstore.sst' from "C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking" Start the HomeGroup troubleshooter. PNRP service recreates the idstore.sst on restart. Hope this helps, Matt

I will try your fix. It is totally amazing that we are in 2011 and Microsoft can not make an OS that will network with another computer running the exact same OS (well one is 32 bit and the other is 64 bit). Edit: The deletion of idstore.sst and rebooting may have worked for me. I am not smart enough to know if Homegroup is working but I can now see both my desktop and my laptop and am successfully transferring GBs worth of picture files from one to the other. So whether it is Homegroup or old fashioned networking, something is happening. Edit2: It is not Homegroup that is working. My detail try at a fix simply enabled an old fashioned network to be repaired. At least there is that. I suppose Homegroup was an idea that the engineers came up with that they simply couldn't implement. Perry

I will try your fix. It is totally amazing that we are in 2011 and Microsoft can not make an OS that will network with another computer running the exact same OS (well one is 32 bit and the other is 64 bit). Edit: The deletion of idstore.sst and rebooting may have worked for me. I am not smart enough to know if Homegroup is working but I can now see both my desktop and my laptop and am successfully transferring GBs worth of picture files from one to the other. So whether it is Homegroup or old fashioned networking, something is happening. Perry

I will try your fix. It is totally amazing that we are in 2011 and Microsoft can not make an OS that will network with another computer running the exact same OS (well one is 32 bit and the other is 64 bit). Perry

Dear Perry, I am afraid no incompetence or arrogance from Microsoft surprises me. They were the company that did nothing but manipulate DRDOS, that made a non-reentrant operating system we were stuck with for some 30 years after the world knew better, that cheated to destroy OS/2, copied Windows from Presentation Manager, raped WordPerfect, destroyed Windows NT (earlier version) and is creator, made a Windows XP operating system that could not deal with the internet, even with its printers, and now cannot use its own networks. That is what happens when we allow a corrupt monopoly to control an important technology.

Hi Matt, Brilliant...I tried your fix and it worked perfectly for me. Thanks for the tip, it saved me hours of troubleshooting. Now I can view and change the Homegroup password, also view others in teh Homegroup which I could not before. Stan