Nice to see that you find this thread and get your problem fixed.
Homegroup removed! How to get network sharing work with Windows 10 v1803.
Here is short description how I get my network sharing work with Windows 10 v1803.
(I haven't never use Homegroup so I start directly from step 2.)
- Only for those PC's which are still using Windows 10 v1709 or older:
Disconnect from non-existing Homegroup if you have used it.
2.1. All PC's: Check Network profile and Network discovery and Share settings
Sometimes this selection to change between Private and Public network profile is missing from Settings / Networks page. In that case profile must change by PowerShell. Right Click Windows Icon (Start button) and open PowerShell (Admin) and use following commands to get interface index number and change profile to Private (or Public):
Get-NetConnectionProfile
Set-NetConnectionProfile -InterfaceIndex <index number> -NetworkCategory Private
2.2. All PC's: Check Network Discovery and Share settings
- All PC's: Set Start type to Automatic and start following services that allow PC's to be visible on Network. (Reboot.)
Push Win Key and type "Services", locate these services.
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- Setting shares.
4.1. Check your current shares.
Open file explorer and type \localhost to address bar to see what shares are made in this computer.
4.2. Create new share (here I use folder "Test").
(Setting "Turn on sharing so anyone …" in Step 2.2. make share for folders in C:\Users automatic.)
Folder is now shared and Network share path is: \PCNAME\Test
4.3. Safe way to share folders.
Create user account to all users on your network to whom you want to give access to shared resources.
Use same user ID and password which they have on their own computers.
Right click "Test" and open Properties and select Security tab to see current settings.
Default security settings are shown in next picture.
Those settings allow access to shared folder(s) only for those users who have user ID on that computer.
4.4. Sharing folder "Test" to Everyone" (Very unsafe setting! Think carefully do you need to select this!)
If you want that everyone have access to that share then go to Security tab and:
- Click Edit
- On Permission dialog click Add.
- New dialog open and you can add "Everyone" to that list https://learn-attachment.microsoft.com/api/attachments/c1f22caa-ec01-4f49-8c76-01b18ed8061f?platform=QnA
- When back to Permissions dialog select which rights you want to give to "Everyone".
Now anyone on your home network should have access to shared folders without credentials or having user account on your computer.
- Now when click Network on File Explorer all your PC's should be visible in Computer and Network sections.
This should be cover the essentials to sharing your data over local network. This share is not limited to C:\Users folder, every folder can be handled like shown in steps 4.
Now your PC's should visible, but if not then try to reset all network settings:
Go to Settings / Network & Internet / Status, scroll down to find "Network reset, on next window click "Reset Now" button.
It will takes about 5 min to perform this reset and then PC reboot automatic.
When you sing in first time you get notification something like "Do you want your PC to be access by other computers", click Yes for that.
If you get error message "Windows cannot access \PC_NAME" when you try to connect shared folders then continue to step 6.
- There is some bug on Windows 10 1803 and because of that PC's can't always connect to each other by Name.
If you get error "\PCNAME path not found" you can solve this by adding your PC's and IP-addresses to hosts file.
6.1 New routers (or modems) may have feature to remember which IP-addresses are assign to each device, but with older routers (or modems) you have to check that your router or modem is set give predefined IP-addresses linked to each PC's MAC-address.
This way PC's will get same IP-address every time when it ask IP-address form router (or modem) DHCP-server.
There should be some kind of list of PC names with MAC addresses and given IP-addresses of each connected PC.
Picture show that list on my router. In my case with old router I had to select manual assignment in each line.
6.2. Add all PC's IP-addresses and Names to hosts file (C:\Windows\System32\drivers\etc\hosts).
You can check your IP-address and PC's name by opening command prompt (CMD)
For IP-address type command: ipconfig you get line like this: IPv4 Address ………. 192.168.100.101
For PC name type command: hostname
Write down IP-address and Name of each PC and add those to that hosts file.
To edit copy hosts file to some another location, right click it and use notepad to edit and save it. Replace original file with edited file. Because hosts file is located on system folder replace will ask administrators rights to perform it.
localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
192.168.100.101 PC1 # Ethernet
192.168.100.102 PC2 # Ethernet
192.168.100.202 PC2 # Wi-Fi
Windows for home | Windows 10 | Files, folders, and storage
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
326 answers
Sort by: Most helpful
-
Anonymous
2018-07-02T16:01:02+00:00 -
Anonymous
2018-06-28T12:57:04+00:00 "Do you want me to create a new User Account on the Win 7 PC with the Win 10 User ID as the account name and using the Win 10 password?"
Yes, that way Win 7 PC should know you as proper user with permission to connect. I have same user account on Win 10 and Win 7 PC's and connections between those PC's work fine without any passwords.
If you are not sure how to do it then don't do it.
As I wrote I test that with different user ID's later this week.
"How do I find my Win 10 user ID? Is it the name showing on the screen at start up when it asks for the Password?, which is my name."
Push Win Key and type Netplwiz (+Enter) when window open click properties to see your local user name.
"Could the router's firewall be causing problems - although none of the settings have been changed."
It shouldn't have nothing to do with that "No permission" issue.
-
Anonymous
2018-06-28T02:12:38+00:00 I also disabled IPv6 on my machines and this seemed to resolve. I am not convinced it is a bullet proof fix.
I found via wireshark that when a client attempted to connect to \ServerName that various name resolution protocols are used to determine the IP address. The IP address is found. However SMB never attempts to connect.
I do not see any TCP connection attempt on port 445.
If I simply attempt to connect to \10.10.10.110 (The IP address of ServerName) then SMB works correctly.
This issue seems to be a problem with SMB not actually attempting to connect to the IP address once it is learned.
However, after the above workaround any subsequent attempt to connect to \ServerName is successful for a while, then after an unknown trigger the problem is back.
This is driving my customers insane.
Anyone else observe the same?
-
Anonymous
2018-06-25T17:06:20+00:00 I can confirm same results.
Computers on Win10 1803 build 17134.112 without table added to the Hosts file in C:\Windows\System32\drivers\etc still have connections issues.
-
Anonymous
2018-06-25T13:22:28+00:00 I did clean install of Win Home 17134.1 to desktop and laptop and test different variations of settings with services running / stopped and then I update to 17134.112 and repeated those same tests.
Both cases ping with names worked both directions, desktop may or may not see laptop but laptop didn't see desktop.
Starting services and PC's see each other, but click PC's icon or entering \NAME may work after restart, but after some time it didn't work anymore.
So I didn't see any improvement and I am going to keep all settings as I have made to get network running correctly.