Windows 10: HomeGroup and network connectivity oddities since upgrading

Update Aug 15th: The network issues have been resolved by modifying SMB2 settings in the registry, as per my posts on page 2. Now, just a persistent HomeGroup error remains.
------------
Ok, first off, a quick run-down on my setup - the "core" of my network consists of a media PC, my primary PC, and my wifes' laptop. Upgraded my PC to Win10 when the "free upgrade" became available, and the media PC yesterday once I decided it likely wasn't going to kill it. Wife's is still on 8.1 and is working perfectly fine for everything, but to be upgraded soon.

All machines are on a 1Gb connection via Cat6 cable through a Gb switch.

Ever since I upgraded my machine to Win10 from Win 8.1 when it became available, I've not been able to access the Media PC via the HomeGroup, or through the network connection that it discovers - when I try, I get an instant (for network browsing. When trying the HomeGroup it takes a fair bit longer to time out, while it looks for other machines) error advising that the location can't be found.

So - what I've found so far is:

• I can't connect to the media PC through Explorer using either HomeGroup or Network (even though Windows has "discovered" it and lists it as a machine on the network)
• Trying to access the HomeGroup, which *should* have three machines in it (mine, the wifes laptop and the media PC), results in an eventual time-out and the message "No other homegroup PCs are available at the moment"
• I can access the wifes' laptop through Explorer without issue.
• I can browse to the media machine via IP address in Explorer without issue.
• I am able to ping the media machine, via host-name, on both IP6 and IP4 without issue. I can also tracert.
• I am able to connect to the machine using the host-name via VNC (am actually doing my diagnostics on that machine via VNC, connected using the host-name)
• I've removed all machines from the HomeGroup, and re-created it with the media PC as the host. Both the laptop and my PC joined it without issue. The laptop can "use" it, my machine times out saying it can't be found.
• I've done an ipconfig /release and /renew on the media PC - it didn't have a reserved IP address in DHCP initially, so guess that it would have changed at some point (both machines run pretty much 24x7, so wouldn't change IP often at all anyway). It's now reserved back to the IP that I know it's been at for the majority of the time it's been up.
• All machines have been rebooted multiple times
• I found an article that suggested that saved permissions may have been an issue, so I removed the cached auth stuff, which also hasn't helped.
• I've checked the WAN settings on my modem and can confirm that the DNS servers are set to those of my ISP (they weren't initially, which has been working for me for years. Set them just to be sure). Modem has been reset a couple of times, also just to be sure.
• There's other stuff I've done, but to be honest, I've looked at, and tried, so much stuff, I've lost track of it all.

I found this article http://www.7tutorials.com/fix-proble...eing-available which seems like it could relate to some of my problems, except I'm running Defender, and that setting they're talking about isn't an option. It IS, however, a Service - which Win10 won't let you stop. There was talk of modifying a reg key to do it manually... but I'm not too sure I want to do that, especially considering I have symptoms other than those relating directly to HomeGroup.

So - if you're still with me, and not fallen asleep from the wall of text (I'd rather put as much info about what I've done/seen/tried up here up front in order to save both you and I some time)... any suggestions/tips on what I can look at/try next, please?

It's VERY rare for me to not be able to track down the source of a problem with stuff like this, so it's vexing me more than a little. Your assistance in helping me exorcise this particular demon would be very much appreciated *Smile

:)

 

I cannot delete the old Homegroup

Original Title: WIndows 10 Homegroup

I'm trying to connect to a Homegroup on my network, we have had a previous Homegroup on the network (Windows 7)

The computer that had the original Homegroup had died a long time ago, (and we cannot bring it back from the dead)

we have since then upgraded all the computers on the network to Windows 10

I cannot delete the old Homegroup to create a new one, no matter what I try..... please help????????

I'm on Windows 10

 

can't view Homegroup network password

Can not connect to my homegroup network after upgrading to windows 10. The original homegroup network password doesn't work and I can't view it in the control panel.

 

No-one? I know it's a bit of an odd one, but figured someone would at least have a suggestion or two?

 

It's helpful to say exactly what error is being reported. I know you said 'location can't be found' but this is not that helpful (try googling that phrase).

Is the error code 80070035, path not found for example? If not, what is it?

 

I had Homegroup problems after I upgraded all 5 computers at the same time on my home network. The old Homegroup was still there, but I did not have the password for it and none of the computers would display it.

I ended up having to turn off all but one computer (including the computer I created the Homegroup originally) and create a new Homegroup on a different computer then was able to change the password and connect the other 4 computers to the Homegroup. Maybe you should start over with your Homegroup.

However one of the computers does not show up in File Manager. I certainly am disappointed fith File Manager in Windows 10 as it shouldn't be this hard for me to copy a file between 2 computers on the network like it is. But that is off topic from your question.

 

Ditto.

My Windows 7 box hosting the shared folder (Call it (A)) is connected by cable, the rest are wi-fi.

That's right, I can see it and the shared folders in file explorer on the win 10 machine (B), but get Error Code 0x80070035 The network path was not found.

• Ditto.
  Ditto.
  Ditto.

I did do a registry key modification - no luck.

Another Windows 7 machine (C) and a Windows 8.1 machine (D) can both access the original Windows 7 machine's (A) shared folder. Only the Windows 10 machine (B) cannot. It would be less infuriating if I couldn't see box A in the Network... almost like it's taunting me!

 

bobdabuilda, you're not alone! There are numerous threads on this or very similar issues. (One of them is here Unable to see Win7.1 shares). I'm convinced that there is something amiss with networking in Win10 and am keeping an eye on the MS community (http://answers.microsoft.com/en-us/w...Threads&auth=1) to see if any solution is forthcoming. I've spent at least a couple of days diagnosing my particular problem and I still feel that I'm at square one. Sorry, nothing concrete to advise but I'll post back if I discover anything useful.

 

Well I also have home group on my computers, its only two computers, one is running win 10 Pro, the other is Win 7 Pro. Had no problem after upgrading one of mine to Win 10 Pro. Only thing I needed to do was enter homegroup password on the Win 10 Pro after upgrade. Mine are hardwired, No wifi at all. What you can try bobdabuilda, is call Microsoft answerdesk right now everyone is getting FREE support for any Win 10 problems. Wait time can be VERY long, best time to try is early in the morning. Good luck.

 

It is hard to reply to threads like this as different errors and different setups are thrown into the mix. And while I am in preach mode, it is never a bad thing to use the forum search tool. As an example, 80070035 error returns some maybe helpful threads.

The OP hasn't replied to my request for the actual error code so that is not helpful.
@Jimbo07, at least you have specified the error code! I know this code well! It has been reported since XP days and I couldn't find any real solutions that worked for me. But I did fix my problem as described here:- Solved Network Shares not seen with MS account - Windows 10 Forums

Don't get me wrong, I can't say that this will fix your problem but at least you should check your registry just in case.

 

My Homegroup had problems with 7, then 8.1 now its completely broken in 10. Although my PCs are connected and show up, I cannot browse them. All I get is a "Can't access \\PCNAME" and it tells me the path isn't found. If I run the troubleshooter, it says the connection was refused. Previously, I could just keep trying to browse and eventually, the share would open.

 

My apologies linw - I got called away unexpectedly for work, and didn't have the login details with me whilst I was away. Also, my apologies for not having posted the error code - I did have it in my notes I made up in preparation for making the post, and turns out, whilst trying so hard to make sure I had tried to think of everything I could to put in there, I missed one of the key pieces of info. Go figure *Wink

The error code when trying to access the WorkGroup is the one you mention in the above post - actually, the one when trying to access it via Network is the same.

I'll have a bit more of a poke around - but am kinda glad that it's just not me having the issue *Wink

 

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 *Wink 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.

 

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.

 

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

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.