New
#21
As you say.
Thank you everyone for your helpful suggestions. However, the problem remains.
Well nothing to lose by trying Network reset.
Start > Settings > Network and Internet > scroll down right hand side to bottom > Network Reset
If you use any special VPN or other customized communication software it may need to be reset.
Hi Caledon Ken,
I have tried a reset on both machines. There has been no change, the problem is still there.
Are both these machines on 1803? any chance the one you are trying to access from is on older Version and still running homegroups?
Not sure where to go from here. I might think about establishing a Password for the user on the machine you can't connect to and then using those credentials to connect.
Hi, they are both on 1803. I did try establishing a password on the machine I cannot connect to but that did not work. I still got the error message and no request for me to enter a password.
Did you delete credentials again?
Could you please shut off router, count to thirty and restart. Can you then try pinging machine you can't connect to.
So your desktop can see and explore files on your laptop.
Your laptop sees the desktop, has it listed in network devices, can ping the other device but can use file explorer to navigate to files.
You've confirmed that on desktop you have enabled share on folder and provided the necessary permissions.
Can you get your hands on another computer, even if a friends for just an hour. Think you have to determine if the desktop is blocking or the laptop has something wonky.
A clean install would clarify but to drastic at this point. Maybe an in place repair on the laptop.
Repair Install Windows 10 with an In-place Upgrade
This is a non destructive process but I always recommend having a back up of personal data.
Ping works fine by name. Remote Desktop also connects fine by name. Only network share access fails, complaining about not being able to resolve the name.
Permissions/credentials issues are easy to rule out by accessing the remote machine shares by IP instead of name. If IP access works, then your permissions/credentials are not the problem. This is the first test everyone should perform, before staring to delete credentials and trying any other random and blind troubleshooting steps.