Network Computers Not Displaying Properly In File Explorer’s Network Section

I have the same problem as many others, according to what I found on the WEB. Often my computers will not display in File Explorer’s Network section. I have set the services Function Discovery Provider Host and Function Discovery Resource Publication the way I found on the NET to correct this problem. I also have a bat file I can run to stop and then start the Function Discovery Resource Publication service. This usually makes whatever computer I run it on show up both in the File Explorer on the same computer it was run on and any other computer that may be powered on at the time. This is a pain, but I never found any other solution until maybe today. Also, maybe I should point out that when the computer I am on does not show up in an open File Explorer’s Network folder, running that bat file only makes it display for that open instance of File Explorer. If that instance is closed and a new one opened and I want the computer to display under Networks, I have to run the bat file again.


A solution I found today is what I need to ask about. I stumbled upon something called Lanman Workstation that an article on the NET claims could fix the problem mentioned above. The author claims that running this command in the command prompt window is a permanent fix: “sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation” I read another article that suggests this:

“How do I enable Lanman Workstation?

Resolution

1. Open the Local Group Policy Editor (gpedit. msc).
2. In the console tree, select Computer Configuration > Administrative Templates > Network > Lanman Workstation.
3. For the setting, right-click Enable insecure guest logons and select Edit.
4. Select Enabled and select OK.”

I don’t know anything about this Lanman Workstation and am wondering if anyone can advise me about it. Would it hurt to enable it as mentioned by using the Group Policy Editor, which by the way, does not open for me in Windows 11 using gpedit.msc, as suggested above. It appears to me now to not be enabled at all. Please see the attachment. However, I have no idea what – 3. For the setting, right-click Enable insecure guest logons and select Edit. And 4. Select Enabled and select OK.” will do. Will that make Lanman Workstation active, and do you think it would do any good to have it enabled? Or would running the code, mentioned above, in the Command prompt window be a better solution? The author of that solution also says, “(you can undo this handiwork by repeating above, omitting /LanmanWorkstation from the end of the string)” This bothers me because if it is actually a permanent solution, why then would I need to reverse it? When he mentions permanent solution, I assume that it does not have to be run every time the computer is rebooted like my bat file does. I do have all shares, permissions, and network discovery set properly on each computer, but this problem has persisted ever since Windows 10 was installed on my computers years ago.

Any help or advice about this would be appreciated.

 

I forgot to attach the file I mentioned above so here it is.

 

Let me try it this way. I tried to find out what is claimed as a permanent fix, sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation, does. If you double click on Function Discovery Resource Publication in services you see its properties. On the Dependencies tab you see what it shows in the first attachment, "Before." After running that sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation, command, you see what is shown in the second attachment, "After." I don't understand what that means or what it does. Can anyone explain it or how it would help?