Windows 10: Accessing shared '\\PCName\Users\Public' Prompts Network Credentials

This is a very strange annoyance. Whenever I initially try to access the public folder on a networked PC named 'WiRNS' from any other PC, I'm presented with this 'Network Credentials' prompt:




Note that it already says in red, "The user name or password is incorrect" when I haven't attempted anything yet.

Here's the really interesting thing. I can enter anything into the "user name" field without any password and I'll get access to the shared public folder. I can enter my name, I can enter an 'x', I can enter anything and it will work but it has to be at least one character long. If I hit enter without any character in the username field, it won't work. Once I get access, I won't be prompted again until the next time I boot up the pc accessing the PC named WiRNS.

I have 5 PCs on the network.
All have local accounts (not using microsoft accounts for login)
All PCs running Windows 10 Pro (2004 but the problem predates this version).
All PCs on the same workgroup (they are not on a domain)
All PCs on the same local network
No PCs have any stored Windows Credentials in the Credential Manager.
All PCs properly set up for public folder sharing for anyone on a private network with password protected sharing turned off (so anyone on the network can access the shared folders).
All PCs see all the other PCs and can access the public folders on the other PCs. Sharing all works except for the annoying prompt to enter (fake) Network Credentials when accessing the shared folder of the PC named WiRNS.
All the public folder share settings on WiRNS match the other PCs

Anyone out there have any thought on what could be causing this?

:)

 

Network Share \\PCNAME vs \\PCNAME.local

Thanks, I know about disabling IPv6 and the difference in \\pcname vs \\pcname\share

Sorry, I wasn't clear ... basically I was doing a test and before I saved any credentials ...
If I accessed the PC by \\pcname or the share by \\pcname\share I got the network path not found vs prompt for credentials, but when using \\pcname.local or \\pcname.local\share I would get prompted for credentials. Once I got prompted for credentials, then the \\pcname or \\pcname\share would start working (i.e. prompt me for credentials vs network path not found). That's why I was wondering what the difference is between \\pcname and \\pcname.local

 

Network Share \\PCNAME vs \\PCNAME.local

Just an observation and I'm not really sure I understand ...

What's the difference between \\PCNAME and \\PCNAME.local ... when accessing a network share ???

I was trying to access a new PC network share by \\PCNAME and kept getting the 0x80070035 error, when it should be prompting me for credentials (see notes). I then accessed it by \\PCNAME.local and it prompted me for credentials which I entered (did not save) and it connected. The share then showed in File Explorer > Network as PCNAME.local ... which it should and I could access it. I then restarted both PC's and the PCNAME.local was NOT showing in File Explorer > Network ... which I expected. I then tried accessing the share by \\PCNAME and it prompted me for credentials, which I entered (saved) and it connected and has been working fine ever since.

Note:
1. I could see the share and access it by \\IPADDRESS (did not save credentials), so I know that all network share settings were correct (i.e. private,discoverable,share/ntfs permissions,password protected, etc)
2. IPv6 settings default (i.e. did not disable IPv6 or set prefer IPv4 over IPv6)
3. SMBv1 NOT Installed
4. Both PC's running Win10 (1803 - 17134.137)

 

Network credential prompt while accessing a public share path hosted by samba

The network topology is as follows:





1, samba server (the share is public)

2, pc1 (win10)

3, pc2 (win10)

4, pc3 (win10)

While accessing samba server from pc1 and pc2, there is no network credential prompt.

While accessing samba server from pc3, I will be prompted with the following popup box.





I can give any valid character in the user name form and login successfully (ofc, it should, cuz it's a public share) .

It is a little strange that why pc1, pc2 do not prompt, but pc3 prompt.

I captured network traffic to check what happened there by wireshark, the capture result shows that both pc1 and pc2 would try logon on to samba by windows account after the message of NTLMSSP_NEGOTIATE, but pc3 would not try to logon on samba server, so
win10 RST the connection and prompt the credential box.

I checked windows credentials on pc1, pc2, pc3, there is no credential for the samba server.

If a add a credential for samba on pc3 by windows credential manager, the prompt would not appear(on pc1, pc2, I do not need to do this step)

Does any one know what the problem there ? I don't want to see the credential prompt, I don't want to add any credential to trick this problem either .

Any suggestion is appreciate , Thanks.