W10 won't see Linux server by name, only by IP Address

For several weeks I have been using W10 with two Linux servers, B767and B777. Until an hour ago, Windows Explorer saw both of them just fine and everything worked as expected.

After a brief hiatus, I came back to the computer and it showed big redXs next to the mapped drives on B777. Windows explorer showed everything just fine for B767.

When I click on B777in the network section of Windows Explorer, it responds (after running the green bar through the address area) with "Windows cannot access \B777" and an error code of 0x80070035 (The network path was not found).

When I click on B767 in the network section of Windows Explorer, it responds by showing the shared folders properly.

I have a Linux workstation and a W10 laptop that both see B777by name just fine.

When I use an IP address to get to B777, I can see and map the shared folders.

I can ping B777by name just fine.

I have rebooted both the server and the workstation and disabled anti-virus and firewall to no avail.

I need some help from someone smarter than me.

Thanks

There is a registry fix for Windows 8 & 10, because of changes Microsoft made with SMB, that it does not play well with Samba. You are going to be best at asking on the forum for the Linux Distro that you are using, since it is a Samaba problem. Most times it is an incorrectly created smb.conf.

Thanks, but I don't understand how that explains why (1) it worked just fine for weeks (2) it works fine on another W10 computer, and (3) The other Linux server is recognized just fine.

Thanks, but I don't understand how that explains why (1) it worked just fine for weeks (2) it works fine on another W10 computer, and (3) The other Linux server is recognized just fine.

Because of updates. I have had Samba break right after applying updates to a unit.

The other problem can be the Windows machines Firewalls. There is a KDE tool to allow you to set up folder shares and also allow you to set up usernames. In reality, Samba is best for a Domain environment than a Workgroup.

Do a search for "Samba Black Book." It is dated, but the best resource out there, same as with the info at Samba.org.

I agree with bro67. I had the same error on one win 10 comp caused by SMB version incompatibility. It used to work then it didn't after an update. My comp had an old registry entry locking SMB to ver 2. My other comps never got answers from requests for shares to be displayed so they responded with the path not found error. And, like yours, you could ping and access via IP no.

I am not pretending to know about Linux but just thought I would add these comments.