HomeGroup and network connectivity oddities since upgrading

Page 2 of 2 FirstFirst 12

  1. Posts : 6
    Win10
    Thread Starter
       #11

    OK - so this got me a little closer to a solution - I can now connect to my media PC via "Network". After checking the reg settings on both mine and the media PC, I found that the media PC did have the SMB2 reg key configured as 0. Set that to 1, rebooted both PCs (just to be sure), and I can now happily browse to the machine via Network.

    However, on my own PC, I am still getting "No other homegroup PCs are available at the moment", even though it found that I had been "invited" to join the HomeGroup, and authenticated the password just fine... so close.

    Off to do some more digging...

    Edit: So, just re-ran the HomeGroup troubleshooter, and this time around it said networking issues were preventing HomeGroup from working. Ran the network troubleshooter when prompted (previously if I've tried this it's said there were no issues), and it's now come up saying that Windows Firewall is preventing connections from @p2psvc.dll,8006 - allowed it to fix that, it then said nothing else to look at.

    So I went back to check stuff - and now not only my HomeGroup isn't working, but neither is my connection to the media PC *or* my wifes laptop via Network lol. Just keeps getting better A reboot has fixed these "extra" issues, but the HomeGroup situation remains. Back to digging...

    Edit2: Looks like I've come up against another "common issue". Managed to get all 3 PCs out of the HomeGroup (figured I'd nuke it all and start fresh). Figured at this point in time, there would no longer be a HomeGroup, and I could create a new one. Hah! That's FAR too logical...

    So now, all 3 machines are reporting that the HomeGroup created by my PC, back when it was still on Windows 7, is out there wanting me to join it. I've cleared the PeerNetworking folder in AppData, I've stopped the services, done a "netsh winsock reset", and recreated the "MachineKeys" folder in the ProgramData directory (with reboots on all machines at the appropriate places). That's me done for now - will need to get back to it tomorrow, I guess.
    Last edited by bobdabuilda; 22 Aug 2015 at 08:53.
      My Computer


  2. Posts : 1,936
    win 10 Insider
       #12

    Hi, Bob. You are forgiven for not replying!!!

    I find it very interesting that you had that SMB problem.

    I wonder if you only have a home group problem now. I have never bothered with a home group myself. They aren't necessary and I just can't be bothered with another layer I can't control!

    Perhaps ditch the home group and see where you are then?

    It can be done and you have cracked the dreaded 80070035 error!!

    Let's keep at it.
      My Computers


  3. Posts : 6
    Win10
    Thread Starter
       #13

    Heh yeah I'll keep digging. I don't like puters beating me

    Main reason for the perseverance on the HomeGroup side of things is the wife - I can deal with mapped drives etc. easy enough, but she's used to using it... I guess I could kinda replicate the HomeGroup with various mapped drives... hmmm. Will keep that in the back of my mind as an option... just sounds to me more like a "retreat" than a solution, though... lol.
      My Computer


  4. Posts : 31
    Windows 10 64 bit
       #14

    bobdabuilda said:
    Edit2: Looks like I've come up against another "common issue". Managed to get all 3 PCs out of the HomeGroup (figured I'd nuke it all and start fresh). Figured at this point in time, there would no longer be a HomeGroup, and I could create a new one. Hah! That's FAR too logical...
    I had a similar problem. I resolved it by selecting a different computer to create the homegroup on. Then I did a shutdown on all but the 1 computer I wanted to use for the new homegroup so that it (newly selected) was the only PC on the network. Then I created the new homegroup on that PC. I then restarted the other computers 1 by 1 and joined the new homegroup. Problem was solved for me.
      My Computer


  5. Posts : 1,936
    win 10 Insider
       #15

    bobdabuilda said:
    Heh yeah I'll keep digging. I don't like puters beating me

    Main reason for the perseverance on the HomeGroup side of things is the wife - I can deal with mapped drives etc. easy enough, but she's used to using it... I guess I could kinda replicate the HomeGroup with various mapped drives... hmmm. Will keep that in the back of my mind as an option... just sounds to me more like a "retreat" than a solution, though... lol.
    That's another reason I avoid homegroups. You should be able to nuke them easily!

    Just wondering, how, exactly, does your wife access the shares? There is 'Network' to bring them all up and individual networked folders can be pinned to the Quick access section of Explorer and shortcuts can be created on the Desktop etc. Just curious as we never needed Homegroup in the 'olden days' and it just seems like another layer to go wrong! Just my opinion, though.
      My Computers


  6. Posts : 2
    Windows 10
       #16

    My solution turned out simpler. It was the Wi-Fi adapter! I thought windows 10 did auto updates. I went to the vendor website and they said they didn't have a windows 10 driver. I swapped adapters and boom! Everything works!
      My Computer


  7. Posts : 1,936
    win 10 Insider
       #17

    Great one, Jimbo. Another one bites the dust!
      My Computers


  8. Posts : 6
    Win10
    Thread Starter
       #18

    oldrock said:
    I had a similar problem. I resolved it by selecting a different computer to create the homegroup on. Then I did a shutdown on all but the 1 computer I wanted to use for the new homegroup so that it (newly selected) was the only PC on the network. Then I created the new homegroup on that PC. I then restarted the other computers 1 by 1 and joined the new homegroup. Problem was solved for me.
    Nice one, glad you got yours sorted, oldrock :) I tried doing the same - and was quite encouraged after all the other stuff I'd done, as when I fired all the PCs back up, the new HomeGroup was there... just that my original issue with HomeGroups was still there/back.

    Rebooted them all again - still an issue. Went through the process again of removing them all, shutting down again (what can I say, I'm persistent!), and the issue was back. Rebooted my PC whilst leaving the other two on... and my HomeGroup stuff is all working...

    I'd love to be able to say "I fixed it!", but after all that, there's no way I could claim that - I think I just had my tongue at the right angle on the last reboot. I certainly don't have any expectation that it'll stay working... but for now, at least I guess I can put this to bed, along with myself... lol
      My Computer


  9. Posts : 31
    Windows 10 64 bit
       #19

    glad you got it working, if not just for now... lol I will say that once I corrected mine I have not had a problem with it. here is wishing you the best!
      My Computer


  10. Posts : 1,936
    win 10 Insider
       #20

    Good luck, hope it 'sticks'.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:09.
Find Us




Windows 10 Forums