Windows 10: net use fails to NAS on same subnet with system error 67 58

Windows 10 Pro 21H2 in workgroupTrying to access share on NAS buffalo in same subnetcmd line elevatednet use r: \\nasserver\images\ /user:nasserver\admin /persistent:yes System error 67 has occurred.The network name cannot be found.net use * \\nasserver\images /user:nasserver /persistent:yes System error 58 has occurred.The specified server cannot perform the requested operation.

:)

 

NAS Disappears and "net view" Fails on non-First Computer to Boot

With the latest build of Win10 (Version 1703, Build 15063.138), our NAS has disappeared from the Network portion of File Explorer on the last of our two computers that boot. Trying to do "net view" from a PowerShell (Admin) window works on the first computer
booted, but on the second it fails with the useless error 2184: "the service has not been started" (and it's more than useless "net helpmsg 1284" suggestion which merely repeats the same worthless phrase). Reversing the boot order reverses the computers
that succeed and fail with "net view". The computer that boots first becomes the Master Browser and is the only one that can see the NAS in the Network portion of File Explorer. On both computers, the mapped Z: drive to the NAS always works and browsing
to the NAS' IP address or hostname works just fine. It's just not showing up in Network.

Feedback Hub link

 

Runtime Broker in build 10586.29 on PC uses 67% of CPU usage with NAS/LAN impact

Hello

Have done the above suggestion many times, but I'm still at the point of not knowing how to identify process/service that is tied to the runtime broker hoarding the CPU and causing 67% usage. Need to know process/service in order to complete all the steps
in your suggested remedy.

Additionally I had a mapped network drive assigned to NAS, which I have disconnected. In doing so the runtime broker has settled down considerably. Maybe you may be able to investigate why a mapped drive to a NAS would cause this problem. The remedy would
be appreciated because I need to map a drive to the NAS.

Thanks

 

Connecting NAS - mapping of drives

Ok,

If you want, we can do a step by step troubleshooting of your current situation:

If you are able to ping your Machine and it responds.
Code:

Try to view if your NAS appears on the Network List:
Code:

If Your NAS appears on the list, try to view it:
Code:

The available shares will be listed there.

Then Try to List the content of one of the directories:
Code:

This should list the content of the directory,

If all this works Try to map a drive on one share:
Code:

Pls reply with the "response" of the first "encounter" of a non positive output.

This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.