Windows 10: HOMEGROUP:File Sharing requires frequent router and computer rebooting

Hi, All. Lots of Homegroup threads here, I see. Here's another! So, I have a Desktop connected to a TPLink WiFI/router via ethernet cable. I have a Laptop accessing internet/home network via WiFi. I use a WiFi Range Extender (TPLink).

I've created a Windows 10 Homegroup (both of my machines are native Windows 10). Using File Sharing to access my files between computers. I can get it working by rebooting router and then rebooting both machines. It works fine for a short period. Once it stops working, I can still see the other computer in my Windows Explorer. However, when I go to Homegroup/User and double-click on the "Documents" folder under the other computer name, rather than opening up a list of all the folders under "Documents" like it does when it is working properly, instead it says "This folder is not available." This is when I need to go through the entire rebooting process, sometimes multiple times, to get it working.

Any thoughts? I've seen some references to using fixed IP Addresses, but don't know if this would work nor do I know how to do it. Or, perhaps it's the WiFi Range Extender? In any event, I'm lost.

Thanks in advance for any help anyone can provide!!!

:)

 

Cannont Delete or Modify Homegroup in Windows 10

This fix did not work for me. I deleted the three files, but after rebooting, the computer is still asking me if I want to join the homegroup which was created by a user that no longer has an account on the computer.

I can share by changing advanced settings not to use homegroups and by turning off password sharing, but everytime Windows updates the computer, it changes those sharing settings and the other computers get locked out. They are calling me on the phone frequently
to fix this problem.

There should be an option on the main computer for any administrator to simply delete the homegroup so a user can start over.

 

cannot open files in public folder on PC #2 from PC #1 in home private network Windows 10 Pro after December updates

"Permission needed to access this file" or "this folder", or similar, appears when opening network/users/public/documents/file x from one of these 2 computers on the other and vice versa. The following status exists on each PC:

• both computers are on same named workgroup; homegroup with same password on each PC; wired directly to the router.
• homegroup is configured to share everything on each computer with the homegroup
• system properties on each computer show the computer is on a business network; when I change to home network and reboot per instructions, the settings automatically change back to business
• Advanced Sharing on each computer shows private network, network discovery on, file & printer sharing on, password-protected sharing turned off
• computer management|system tools|shared folders|shares|Documents\c:\Users\Public\Documents is shown as a default share

So how can I share files in public folders on my network the way I used to (worked flawlessly on Windows 7 Pro with same setup)?

 

Homegroup has always been a pain as it uses ipv6 its better to remove it and just use the normal workgroup and disable ipv6 as its not used for anything else. Do all pcs get a ip in the same range ie 192.168.0.1, 192.168.0.12 some exteneder change it. The other thing is the master browser when you look to connect windows doesnt search it asks a pc that is master browser for details if thats out of date it wont be seen the same. run this util and see if it sees everytthing and mnote the master browser NetBScanner - NetBIOS scanner

 

Thanks Samuria. I ran on both machines. Desktop, which is the Master Browser, is getting assigned to 192.168.0.123. Laptop, which is not a Master Browser, is getting assigned to 192.168.0.108. Does this tell you anything?

I have not yet disabled ipv6. If I do, will Win10 automatically revert to ipv4?

 

Ipv6 isnt used for anything at the moment but homegroups so ipv4 is the norm. There are known problems with sharing etc on some builds. You need to start the MB first or it will change running the scan again can often kick things back into life. The problem is the MB can take a while to update there are some work arounds on MS https://partnersupport.microsoft.com...ab08363?auth=1

 

Thanks. I wish I was more tech-savvy, but this stuff is pretty far over my head. I wasn't aware that I was actually doing anything to "start the MB". Can you clarify? And, the Microsoft link you provided was also way over my head.