Windows 10: Equivalent or alternative to the "netdiag" command for Win10

the "netdiag" command is not available in Windows 10. Is there any equivalent available?

Apparently netdiag was last seen in Windows XP. Since then we've had the Troubleshooters and netsh....

Windows Vista includes the Network Diagnostics Framework (NDF), a set of technologies and guidelines that allows a collection of troubleshooting tools to assist users in diagnosing, and where possible, automatically correcting networking problems.

https://technet.microsoft.com/en-us/.../ff625276.aspx

Thank you Bree & bro67. In answer to the latter's question, the issue is that my Synology NAS does not show "network" in Windows explorer. Neither does it when I search by name or IP address. The same when I try to map it to a network drive from Windows explorer. As a workaround, I was able to use the map network feature from within the Synology set of commands. As I had tried what seemed to me to be all the relevant windows "commands" with no obvious problems being shown, I thought the netdiag command might reveal something. So this is not an urgent issue as my network is functional

I should add that I am running Windows 10 (most recent update) using static IP addresses with homegroup and netbios over TCP/IP disabled so that the PCs on my network are connected through WSD discovery. I arrived at this point through a rather tortuous, lengthy and frustrating process of searching the internet and trying various suggestions to fix what appears still to be a widespread Windows 10 problem where network devices do not show up on a LAN or do so erratically with no apparent rhyme or reason.

The SMB 1.0/CIFS windows feature is enabled and I'm reasonably sure always has been. Could you please confirm I need to use Power Shell with your instruction for then disabling it i.e. to past into the text that starts with "sc.exe ....." I have to admit to sticking with Command Prompt thus far with WIndows 10!

On SMB and the the NAS - it is presently set to SMB3 max, SMB1 min. I assume I should not change the minimum to 2 until after disabling SMB1 on the PCs.

On the the Master Browser, I should explain that my path to "fixing" this issue seemed to consist more of a series of workarounds than what I would consider real fixes. One of the earlier such "fixes" that produced an improvement related to Master Browser voting. The problem would either re-appear or get worse when the Master Browser function was voted off one device onto another. After a series of experiments, it seemed clear that having the NAS as Master Browser resulted in a stable network listing on all devices. Consequently, I disabled the Computer Browser service on the two PCs and two laptops on the network in order to prevent any changes. Probably not the most elegant way to bring that about, but it was simple and worked!

As far as I can tell, it was disabling the Computer Browser service that caused network discovery to change from Netbios to WSD. And that, along with a number of other suggested fixes I had come across, was what set me on the course to disabling TCP/IP on the network cards.

Thanks again for for responding to my posts.