User caused access to the network resourse denied map DOA

Question

An inexperienced user used the user icon to access the open user, access to the network resource is now denied and the mapped drive stopped working, Done everything

Items in bold are the latest. Because of new info on the case and additional work done

the access to the main pc over the network using correct credentials for a user on that pc seems to be denied claiming

"\ [peer server] is not accessible you might not have permission to use this network resource.........."

**We implemented a MSFT suggested solution on both machines activating the Guest account which did not work. This has broken a networked app requiring read and write access to the directory involved over the network. This has produced a costly hardship on the business. Business continuity issue **

The pcs are on the same subnet, wired to the same router and both are in the workgroup "workgroup".

PCs were originally set to use password protected access as using the other radio button 'turn off' did not work.

I tried resetting it both ways.

file and printer sharing are on.

Network is set to private.

Permissions were set to everyone, full control when i originally set it up.

I still had to map the drive originally using credentials from an admin user on the peer server.

By peer server I mean a pc with a directory shared out of the drive to allow a small accounting program to access the main file from both pcs.

What am i missing here?

We are going to be replacing the client to try to allow non-password access but i am unsure this will work. We also checked the firewall and made sure it included the local ip range

Please be kind and reply

TIA

Answer 1

First let me clarify the client could see the peer server over the network. Not sure about the client being seen by the server.
Also server is running w10 pro as I believe is the client.

I can't remember if the server could see the client.

Both units had an ip address provided by the router.

DNS client, fdrp host and FDResPub, and UPnP device host were set to run automatically delayed start. Not sure about SSDP Discovery.

We checked allowed apps also while we were there if i remember correctly Network discovery was allowed. I cant find the sheet i was working with on allowed apps, however I remember I allowed obvious network protocols .

I did notice Peer Name resolution protocol PNRPSvc, and Peer Network grouping P@pSvc would not start because it was unable to access a key required dependency for start.
This occoured even after reboot.

Answer 2

Did not need a dns server previously other than the one yr old router be fore the issue. I thought the name was provided by the peer.

Why would i need a second DNS server and How would i set it up and point to it other than in ip address under network. or set
a name server?

Any other suggestions?

Some how I lost your answer. Let me say I was not trying to be rude but sometimes the obvious question must be asked or sometimes
there are holes in someone's experience. So please repeat your answer as I did not get to print it out because of hardware issues.

Thanks