Windows 10: Can't See Shared Win10 Machine/Seeker in workgroup but shows in domain

I have scoured the Networking and Sharing portion of this Win 10 Forum for an answer to my issue but have not found anything that works.

We have a peer to peer network, with one Win 10 machine (acting as server - which we call server) which shares several hard drives for everyone in the office to access. It has network discovery on, file and printer sharing on, turn off password protected sharing off. It has all the drives named and shared properly so everyone has full access. All the other Win 7, and Win 8 machines have complete access as designed. Another Win 10 machine has complete access as designed. All machines are part of the same workgroup Engineer. My machine is a Lenovo laptop which was upgraded from Win 8 to Win 10. When I try to access the Win 10 machine (which is acting as server), I get the Enter Network credentials pop-up asking for Username and Password which we do not use nor have ever set up on the Win 10 machine or any other. I know that there are several posts that have the Enter Network credentials popping up, but the difference is that their screenshot showed them as part of a workgroup. See the following:




When I get the same pop-up on my Lenovo Laptop It looks like the following:





My System Properties information:





Notice that the example above which is part of the workgroup has no reference to a domain. My pop-up on the Laptop shows reference to a domain, and whats interesting is that the domain is the computer name of the laptop itself. There are no domains set up on any machine of our peer to peer network. I think what needs to be done is the Laptop needs to be convinced it is not part of a domain but part of a workgroup called Engineer, and that might be one step in solving the problem. I wouldn't doubt that after solving that issue that a lot of the others listed in other threads will rear their ugly heads afterwords, but who knows, knowing how to resolve that might solve all my problems. Any ideas community?

Thanks in advance for your help.

:)

 

Cannot get 10 to recognize other win 7 computers in a workgroup after being set to share

No there is no server and thus no domain just a peer workgroup. Yes the error states that there is no such network path. I have found that I can access the shares via command line with IP addresses. At first I could not open the shares however until I
discovered that giving share rites to everyone did not show up as security rites. After I added everyone to the security rights I was able to access the shares with command line IP addressable shares. So I guess my questions morphs to why can't the win10 machines
see the Names of the private Lan computers so they can be accessed without resorting to IP addresses. Why isn't internal local network communication providing this data to the windows 10 computer?

 

After the 1511 update, the windows 10 pc's cannot see other shares if it is not the master browser

Thanks for replying. Still the problem remains: the windows 10 machine cannot see all the shared pc's, only itself and a windows 7 pc. not even a windows server 2012r2 datacenter in workgroup mode(no domain). It has to be the MB to see all pcs and shares

 

No one has seen this problem?

 

Are you using a Microsoft account? I've had trouble accessing shares from within a Microsoft account. The only solution was to create a Microsoft account on the host machine and log in to that. The other solution is to use a local account to access the share.

Just a stab in the dark.