Can't access NAS by name

Yesterday I did a clean (re)install of Windows 10. All seemed ok, but today I cannot access a NAS disk by name. I can access it by IP address, and nslookup correctly resolve both name and addresses. But if I try to access \\MyBookLive (I know, - a cleverly original name.) - I get an error saying "Windows cannot access \\MyBookLive", giving an error code 0x80004005.

For the time being, I've mapped the IP address so I can access the drive, but I recall getting security warning popups in the past when I've done that so I hope this is temporary. And the IP address is set DHCP so I can't guarantee it will stay the same.

Any idea how to resolve this?

WD has some useful applications. Try WD quickview, it will give quick access to state of drive and also a way to go to drive.
Just a suggestion.

Also host name may have changed with some firmware updates.

The WD application that maps drives seems to use the address rather than name of the server. Two other PCs are accessing the server by name so I'm pretty sure the name hasn't changed. (But that doesn't mean I used the right name or specified it correctly in the Map process.) I'll dig around some more.

Do you have network discovery turned on? New installations of Windows sometimes needs few days to get all connectivity...

Yes, I have network discovery turned on ... at least on the place you showed. I don't know about other options I might have wrong. In a detail display of the Network part of the file explorer display, Windows says it uses SSDP to discover the NAS server. I have no idea if that's what I should be using (or how to change it if it's not right).

I found a thread on WDC forums and some possible solutions to your problem.

If you didn't already, you ca read the from this post on...

I've now read that post - I had missed it. I'm a little reluctant to mess with the LAN Manager Security Level because

1. it worked on the now problematic PC before I did a clean reinstall of Windows 10 (although sometimes not right after a reboot)
2. it works correctly on 2 other PCs - 1 running Win10, the other running Win7. I didn't have to do anything special on those PCs.

Must agree with you. It works for me on Windows Insider and on RTM Windows 10 with clean install.

Try first with some of the WDs tools. I will come back on the (my) afternoon.