I can't see my windows 11 pro pc in my network

Question

I have tried everything from the above and no change. I have a network of 6 pc's (5 windows11 pro and 1 windows 10) all linked via a switch. The folder shared from a windows11 pro is not see in the network by 2 of the windows 11 pcs(one of them is the one who has it on the hard drive). I don't have save changes button at all in CHange sharing options for different network profiles...it just doesn't exist on those 2 pc...I really don't know what to do, called microsoft 80 mins no answer.

May I mention they are all members of the same workgroup(not that I can change it from the windos11 pro pcs) and set even individual ip address in tcp/ip4; deactivated tcpip6.

do you have any advice?

Answer 1

Hello,

Thank you for posting in Q&A forum.

Based on my understanding of your issue, I suggest you try the following steps to see if it can be solved:

1. Go to Control Panel > Network and Internet > Network and Sharing Center > Advanced Sharing Settings, enable network discovery and turn on file and printer sharing in private or public networks.

2. Open Services in the search bar in the lower left corner of the computer, and make sure the services mentioned below are started (running) and their startup type is set to automatic.

DNS Client

Function Discovery Provider Host

Function Discovery Resource Publication

Server

SSDP Discovery

UPnP Device Host

I hope the information above is helpful.

Best regards

Zunhui

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

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

See OPTION TWO in this link. Open a command prompt with "run as administrator" and run the posted netsh commands.

https://www.tenforums.com/tutorials/49753-turn-off-file-printer-sharing-windows-10-a.html

Also see my answer in this post.

https://learn.microsoft.com/en-us/answers/questions/2151284/24h2-killed-network-discovery

I posted a Powershell script that checks the status of the required network discovery services. Run that script on working and non-working pc's and see what it finds. Does the script report that "Your network profile is set to Private." on all pc's?

If you have services that aren't running, you can use the script that I posted in this link to enable them.

https://learn.microsoft.com/en-us/answers/questions/302088/how-to-switch-from-a-call-by-ip-address-to-a-call

Answer 3

I have tried, still no luck.

I used your script in powershell and this is the answer I got:

Your network profile is set to Private.

If you don't get any more messages, then everything checks out.

SSDP Discovery is not set for automatic startup.

Rule NETDIS-UPnPHost-Out-TCP is not applied to private networks.

Rule NETDIS-NB_Name-Out-UDP is not applied to private networks.

Rule NETDIS-NB_Datagram-Out-UDP is not applied to private networks.

Rule NETDIS-LLMNR-In-UDP is not applied to private networks.

Rule NETDIS-SSDPSrv-In-UDP-Teredo is not applied to private networks.

Rule NETDIS-UPnP-Out-TCP is not applied to private networks.

Rule NETDIS-NB_Name-In-UDP is not applied to private networks.

Rule NETDIS-NB_Datagram-In-UDP-NoScope is not applied to private networks.

Rule NETDIS-WSDEVNTS-Out-TCP is not applied to private networks.

Rule NETDIS-UPnPHost-Out-TCP-NoScope is not applied to private networks.

Rule NETDIS-WSDEVNT-In-TCP-NoScope is not applied to private networks.

Rule NETDIS-WSDEVNT-Out-TCP-NoScope is not applied to private networks.

Rule NETDIS-LLMNR-Out-UDP is not applied to private networks.

Rule NETDIS-WSDEVNTS-In-TCP-NoScope is not applied to private networks.

Rule NETDIS-SSDPSrv-In-UDP is not applied to private networks.

Rule NETDIS-DAS-In-UDP is not applied to private networks.

Rule NETDIS-NB_Datagram-In-UDP is not applied to private networks.

Rule NETDIS-UPnPHost-In-TCP is not applied to private networks.

Rule NETDIS-NB_Name-In-UDP-NoScope is not applied to private networks.

Rule NETDIS-WSDEVNTS-Out-TCP-NoScope is not applied to private networks.

Rule NETDIS-UPnPHost-In-TCP-Teredo is not applied to private networks.

Rule NETDIS-FDRESPUB-WSD-Out-UDP is not applied to private networks.

Rule NETDIS-WSDEVNT-Out-TCP is not applied to private networks.

Rule NETDIS-WSDEVNTS-In-TCP is not applied to private networks.

Rule NETDIS-SSDPSrv-Out-UDP is not applied to private networks.

Rule NETDIS-NB_Datagram-Out-UDP-NoScope is not applied to private networks.

Rule NETDIS-FDPHOST-Out-UDP is not applied to private networks.

Rule NETDIS-WSDEVNT-In-TCP is not applied to private networks.

Rule NETDIS-UPnPHost-In-TCP-NoScope is not applied to private networks.

Rule NETDIS-FDRESPUB-WSD-In-UDP is not applied to private networks.

Rule NETDIS-FDPHOST-In-UDP is not applied to private networks.

Rule NETDIS-NB_Name-Out-UDP-NoScope is not applied to private networks.

Rule NETDIS-FDPHOST-In-UDP_1 is not applied to private networks.

Rule NETDIS-FDRESPUB-WSD-In-UDP_1 is not applied to private networks.

Rule NETDIS-FDPHOST-Out-UDP_1 is not applied to private networks.

Rule NETDIS-SSDPSrv-Out-UDP_1 is not applied to private networks.

Rule NETDIS-FDRESPUB-WSD-Out-UDP_1 is not applied to private networks.

Rule NETDIS-DAS-In-UDP_1 is not applied to private networks.

Rule NETDIS-SSDPSrv-In-UDP_1 is not applied to private networks.

Rule NETDIS-LLMNR-Out-UDP_1 is not applied to private networks.

Rule NETDIS-UPnP-Out-TCP_1 is not applied to private networks.

Rule NETDIS-LLMNR-In-UDP_1 is not applied to private networks.