Network PC Win10 1903 issue, PC can see each other, one can browse

Hi, i know this topic is probably done to death, but ive tried everything I can think of googling and looking around on win 10 forums and nothings helped.

I have one PC (HomePC) and another windows 10 1903 pc (MEDIAPC). HomePC can see MEDIAPC, but i get
"Windows cannot access \\mediapc check the spelling of the name... " etc. error. Ive done all the normal trouble shooting.

MEDIAPC can see HomePC and browse shared folders. I uninstalled MEDIAPC network drives and reinstalled them. ive gone through services. etc.

There has to be a fool proof method of getting this problem solved. why is it so difficult to network windows 10 pcs? why did MS remove homegroup? i never had any problem with homegroup's

EDIT: furthermore, ive added a laptop to the problem. "LAPTOPPC". laptop pc can see MEDIAPC and browse. MEDIAPC can see LAPTOPPC and browse. LAPTOPPC CANT SEE HomePC. HomePC CAN SEE LAPTOPPC, but access is denied. here i thought the problem was with MediaPC, but i think the problem is with HomePC?

I also get the following error when I try "ctrl - r" and type "\\192.168.0.94\c" I think it might have something to do with trying to connect with the wrong username + password at one stage?

Have you tried to connect without the "c" in the path-name.

Code:

\\192.168.0.94\

I would try the same thing again but use the computer name.

Code:

\\mediapc\

If this does not work use the ping command to check the computer name

Code:

ping -a 192.168.0.94

This is an example from my pc to another pc that is named "pi11"

Code:

C:\Users\Owner>ping -a 0:0:0:0:0:ffff:c0a8:c80b
Pinging pi11 [192.168.200.11] with 32 bytes of data:
Reply from 192.168.200.11: bytes=32 time<1ms TTL=64
Reply from 192.168.200.11: bytes=32 time<1ms TTL=64
Reply from 192.168.200.11: bytes=32 time<1ms TTL=64
Reply from 192.168.200.11: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.200.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

In your first post you tried a bunch of stuff did you try to stop and start "Network Location Awareness service" or NLA for short.

Here is a quick tutorial on that
1 press the Windows key + R
2 type in "services.msc"
3 Scroll down to "Network Location Awareness"
3 Click on Stop, It will warn you of other services that will also be stopped but click "yes"

It should look like this


Within a minute or so the services should stop -- and then start again on their own, If not restart them.
These are the service names.

Code:

Network Devices Auto-setup
Network list service
Network Location Awareness

You may need to do this more than once to actually stop network location service, You may also have to restart the services more than once to get them all running.

If you are able to connect after all of the above open "Network Location Service" again and set the "Startup up Type" to "Automatic (Delayed Start)"

Is your network on public or private, If your not sure how to find that press the windows key and type in or paste this network status (you don't need a box to type or paste into a search box will open as soon as you start)

It should be on private.