My solution to missing local computer name in the Windows 11 Network folder

Version


As I say in the title. This is my specific solution, but it might work for others who have a mixed home network of Windows 10 and Windows 11 PCs (laptops or desktops).
I've been at this for about four weeks and I've been at my wits end to try to figure this out. It's apparent to me that Microsoft has a problem with the discovery and browser hosting services. I wish they get it together and solve this problem.

The table contains all the working settings. If you have one or more of the Windows 10 and or Windows 11 PCs in your home network. You might have to play with this configuration a little more. The key is to determine which Windows 11 PC you want to make or host the MSBROWSE list. If it's not, the Network folder on the Windows 11 PC won't display its own local computer name. Windows 11 needs SMB to make that work even though Microsoft doesn't want users to use the protocol. My response, then fix your dang discovery host/publication service.

Test verification was to cold start each PC and make sure the Windows 11 PC was hosting the browse list regardless of which PC entered the desktop first. Open the File Explorer, navigate to the Network folder and make sure LAPTOP01 and LAPTOP02 were visible in the folder list.

If you can access a 'missing' network computer by entering its name in File explorer's address bar
\\COMPUTERNAME
then that proves that the network is operating correctly and that your only problem is that it was not being shown within File explorer's Network section [which is a chronic File explorer shortcoming not a network fault].


You do not need SMB1 for a network that only contains Windows 10 & Windows 11 computers.
But, if I have understood you correctly, then you are suggesting SMB1 as a means of making File explorer, Network section display correctly.


All the best,
Denis

That's exactly what I'm suggesting. SMB is the only workable solution to making that local computer name visible (and stay visible). And if the Windows 11 isn't the browse host, there are other negative side effects that occur in the home network.

I agree, File Explorer is garbage right now. MS needs to fix it. I rather not have to use SMB. Having to type the \\computer_name, setup net drives, or pin shortcuts of the \\computer_name are alternatives that I don't like. MS implemented the File Manage Network folder, then make it work. They do have a test group, don't they?

OK, I understand now. You are addressing the problem with the File explorer, Network section rather than any network faults.
Personally, I gave up on File explorer. It's been faulty since, I think, Windows 10 Version 1803. I use network shortcuts instead.


All the best,
Denis

---

Welcome to ElevenForum.

It's really worth making time to browse through the ElevenForum Tutorial index - there's a shortcut to it at the top of every ElevenForum page [within the Tutorials dropdown list].
- At the foot of the ElevenForum Tutorial index is a shortcut to download it as a spreadsheet.
- I download a new copy each month.
- By downloading it as a spreadsheet I can benefit from Excel's excellent filtering capabilities when I search for topics of interest.
- ElevenForum tutorials are also listed at Tutorials and there's a shortcut to that at the top of every page.

You can search ElevenForum using the search box in the top-right corner of all ElevenForum webpages or using Advanced Search - ElevenForum
- You can also search ElevenForum threads in many general search engines, such as Google, by adding site:elevenforum.com after your search term. For example,
Taskbar setup site:elevenforum.com
- [This is what the search box in the top-right corner of ElevenForum webpages does automatically]

For MSOffice problems search in and, if necessary, create threads in the TenForums MSOffice section [ElevenForum does not have one].

lintek214 said:

SMB is the only workable solution to making that local computer name visible (and stay visible).

Click to expand...

I see you have enabled the 'SMB 1.0/CIFS Server' feature on your PC. SMB1 is a security risk, and the Server is the most vulnerable part of it. You don't even need it to aid your networking issues. The Client alone is sufficient for that, turn off the Server ASAP.

Bree said:

I see you have enabled the 'SMB 1.0/CIFS Server' feature on your PC. SMB1 is a security risk, and the Server is the most vulnerable part of it. You don't even need it to aid your networking issues. The Client alone is sufficient for that, turn off the Server ASAP.

Click to expand...

I tried without the server portion. Didn't work either. Microsoft really gummed up the networking. Like I said, without doing just what I outlined (for myself), there were other negative side effects. Not having all the SMB components installed was one of them. This is my specific solution and a possible template for others. I'm not making any claims what I did will work for others. MS has forced users to do things to their network hardware and software to make a simple network work, that virtually no one can claim one fix fits all. I read post where the replies were that the user should re-install Windows and users do it. That's freaking crazy.

Oh, I'm behind an internet provider's router that 99% of users have. Most routers have sufficient firewall protection which I trust. Zero chance that SMB server port is open to anyone on the other side. Try Shields Up at Home of Gibson Research Corporation

lintek214 said:

Microsoft really gummed up the networking

Click to expand...

It's your comments like this that make me worried about misunderstandings in your thread.
- Microsoft have not really gummed up the networking.
- Microsoft really gummed up displaying the File explorer, Network section [presumably because of faults in the Windows components behind it].
- Not the networking. Your earlier testing confirmed that your network works.

lintek214 said:

MS has forced users to do things to their network hardware and software to make a simple network work

Click to expand...

I have never been let down by this procedure.
A consolidated network setup checklist for Windows 10 and 11 - my post #4 - TenForums
You are right to anticipate different people having different experiences.
- Several forum members have used this procedure successfully.
- Some forum members have reported network problems despite using this procedure.
- In some cases, they've helped me to improve the procedure & they've been able to resolve their network problems but some people have nevertheless reported continuing network problems.
- The procedure has evolved over a couple of decades from Belkin network adapter installation instructions that were the first intelligible networking instructions I had ever seen.
- Over the years & on nine computers of my own, I have used this procedure with WinMe, WinXP, Windows 7, Windows 10 & Windows 11.


All the best,
Denis

Try3 said:

It's your comments like this that make me worried about misunderstandings in your thread.
- Microsoft have not really gummed up the networking.
- Microsoft really gummed up displaying the File explorer, Network section [presumably because of faults in the Windows components behind it].
- Not the networking. Your earlier testing confirmed that your network works.

Click to expand...

I tried explaining this in another thread. It made ended up with me blocking that person because of the arguments.

No matter what, if something does not work the way they want it to, most people seem to think all of it is broken. And I hope you have better luck than I did trying to convince people otherwise. Because that is exactly what I was saying and it was like talking to a brick wall.

I'm not trying to be argumentative, but you're the only one that mentioned the word "broken", not me. You might say I inferred the term, but that would just your opinion. Of which, I stated my opinion as to my "specific experience". I gave a sound reason to my problem and a possible template to a solution. No more or less than anyone else discussing this topic in another thread. I can't control the conclusions one makes from my statement, but I have or had no intension of misleading anyone. I believe my thoughts are straight forward and honest. No brick wall on my part because I'm willing to try anything within reason to fix a problem. It's unfortunate the Microsoft doesn't seem to be will participant. I say that with sadness because for years users have had issues with their implementation of home networking. That's fact.

lintek214,

As long as you recognise that problems in File explorer, Network section are File explorer faults rather than networking faults then you won't waste your time investigating the wrong topic.
It's just that your choice of words keeps leaving me concerned that we're talking at cross-purposes. For example

lintek214 said:

users have had issues with their implementation of home networking

Click to expand...

All the best,
Denis