Why doesn't NET VIEW work on W11, but does on W10?

I've got a basic simple NETWORK., Router with a USB drive shared on it, 2 PC's, one W11, the other W10. A printer and scanner as well.

 

On W11, NET VIEW returns an Error 53., one W10, shows me all the connected devices?

 

If I use on W11 NET VIEW \\share_name, it works fine.

 

On Windows File Explorer, on W10 it sees both the W10 PC and the W11PC and I can drill down and see the contents of the drives on the PC's. W11 shows me only the W10 PC, printer, scanner and some other non-PC device, including the Router and the USB drive attached?

 

I have on W11 SMB fully enabled. Searched the web for the problem and DID all the setting and Services verified to be correct?

 

I am at a loss? I did have Wifi 6 router before with an Intel M.2 AX1650i card. It didn't work then either, and now, I'm on Wifi 7 with an Intel BE200 M.2 card, and the problem persists. 2 different routers and M.2 cards, so I assume this IS not Network itself related.

 

This does appear to be from Google searches a common problem, but it seems most are easily solved with some settings changes? Doesn't work for me?

 

Any ideas? This has been going on for months.

 

For example. some DOS CMD's:

 

==================

C:\>net view
System error 53 has occurred.

The network path was not found.

==================

 

But this works if I try to see the router and its USB drive::

 

==================

C:\>net view \\tp-share
Shared resources at \\tp-share


Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
G           Disk
The command completed successfully.

====================

 

Makes no sense.

 

I've tried it with the W10 PC off as well, as I sort of suspected a Master Browser (that does not exist) problem), and the results are the same.

 

Welcome to BC.

 

NOTE : OP has Topic Here : https://www.elevenforum.com/t/win11-net-view-problem-on-lan-w10-and-w11-differences.23865/

 

Note : it is impolite to Topic Shop and to have 2 or more sites with Volunteers looking for  a answer.

 

Edit : Add welcome.

Edited by Pkshadow, 29 May 2024 - 08:31 PM.

Would be best to list what you have done or seen since we have no idea and as well do not want to duplicate anything.

 

Have you seen this. : https://learn.microsoft.com/en-us/answers/questions/957194/windows-11-smb-client-cannot-connect-to-smb-share your error 53

 

Is part of this page : https://www.google.com/search?client=firefox-b-d&q=W11+NET+VIEW

Also is network discovery enabled?

Turn on file and printer sharing on the network adapter. Per MS below It's not installed by default because it's so old and stuff like ws-discovery have taken its place. See last paragraph. Below is a copy and paste from Microsoft about error 53

To resolve this problem, make sure File and Printer Sharing for Microsoft Networks is enabled. To do this, follow these steps:

Log on to the computer by using administrative credentials.
Double-click My Computer, double-click Control Panel, and then double-click Network and Dial-Up Connections.
Double-click the network connection you want to modify, and then click Properties.
On the General tab in the Components checked are used by this connection area, locate File and Printer Sharing for Microsoft Networks. If it is not listed, install it by clicking the Install button and then double-clicking Service.
Make sure that the check box next to File and Printer Sharing for Microsoft Networks is selected. This setting makes shared resources available on the network.

More information
File and Printer Sharing for Microsoft Networks is equivalent to the Microsoft Windows NT 4.0 Server service. If you do not want to share resources on a connection, disable this option in the properties of the connection. Windows 2000 Active Directory requires that File and Printer Sharing for Microsoft Networks is enabled on domain controllers for fundamental tasks such as propagation of the SYSVOL share by using

@ginandbacon must Cite Source and provide URL.  Not good enough : "Below is a copy and paste from Microsoft about error 53"