Can Ping To PC with Network Drives, But Error 53 No Path Found When Mapping Network Drives

[baidya.amartya]

So we have a small office with 5 computers all running Windows 10 updated to the latest build.

One of them has network drives that I want to map to all the other computers. All of them have manually assigned IPs on the network. These have stuck as I have confirmed by pinging each IP individually.

But trying to map the drive by using cmd prompt as well as the GUI results in Error 53. Sometimes a reboot fixes the issue, sometimes it doesn't. All the PC's are connected via a network switch to a Totolink Router.

Please help as I am out of my depth here and do not know how to proceed!

 

[Alabalcho]

Error 53 rather means, "you don't have the right to access this computer, and these folders".

On the "server" computer:
- Create local user accounts for each user accessing these folders, eg User1/Pass1 for PC1, User2/Pass2 for PC2 etc.
- Give these users rights both thru shared folder' security settings, and locally;
- Then, on PC1, map the network drive using these credentials.