Windows 11 Empty network folder

[tmarsh]

My GMKTEC M7 Pro mini pc consistently shows an empty network folder. Occasionally on a boot it will populate but then contents disappear. Internet access is OK, occasionally takes two or three tries to connect to a site. I recently set up a NAS on a Beelink Me Mini running Truenas Community and cannot get shares to work. I dual-boot with Linux Mint and they work fine there. I've enabled/disabled smb1 and updated the network card drivers but the problem persists. Any ideas?


Windows Build/Version Windows 11 Pro 24h2

 

[ChatGPT]

Thanks — that’s a common class of problem (Windows sees an empty Network folder / intermittent share visibility while Linux can see the NAS fine). Below is a short, practical checklist to narrow it down plus the most likely fixes. I’ve pulled common causes from other forum cases (SMB/Discovery/service issues, NIC power/driver problems, firewall/AV interference). n an elevated Command Prompt and run:

• ipconfig /all — confirm IP/subnet/gateway/DNS.
• ping <NAS_IP> — verify basic reachability.
• net view \<NAS_IP> — see whether Windows can list shares by IP.
• explorer \<NAS_IP>\ — try opening a share directly by IP (this bypasses discovery).
• In PowerShell (admin): Get-SmbClientConfiguration — note client settings.
  • Try mapping a share by IP (File Explorer → Map network drive → \<NAS_IP>\share). Report any error code.

If the share works by IP but the Network folder is empty

• This strongly points at discovery (SSDP/UPnP/Function Discovery) or name resolution, not TrueNAS itself. Windows discovers devices using SSDP/Function Discovery — if those services are stopped or blocked the Network view will be empty even though direct access by IP works. See similar troubleshooting advice here.

Immediate things to check / fix (do these in order)

1. Network- Settings → Network & Internet → Ethernet (or Wi‑Fi) → Advanced network settings → Ensure the network profile is Private.
   • Settings → Advanced sharing options → Turn on Network discovery and File and Printer Sharing (Private profile).
   • Temporarily turn off Password protected sharing to test.
2. Required Windows services (PowerShell or Services.msc)
   • Ensure these services are running and set to Automatic (or Automatic (Delayed Start)):
     • Function Discovery Provider Host (fdPHost)
     • Function Discovery Resource Publication (FDResPub)
     • SSDP Discovery (SSDPsrv)
     • UPnP Device Host (upnphost)
     • DNS Client (dnscache), Workstation (LanmanWorkstation), Server (LanmanServer)
   • Quick PowerShell check (run as admin):
     • Get-Service -Name fdPHost,FDResPub,SSDPSRV,upnphost,LanmanWorkstation,LanmanServer
   • If any are stopped: sc config FDResPub start= auto & net start FDResPub (repeat for the others).
   Many users solved “NAS appears intermittently / Network folder empty” by restoring these discovery services.
3. Access by IP and DNS/NetBIOS name resolution
   • If \<NAS_IP>\ works but \NASNsts file entry (C:\Windows\System32\drivers\etc\hosts) with NAS IP/name OR set a DHCP reservation + local DNS/NetBIOS registration on your router.
   • NetBIOS over TCP/IP can help older devices: adapter Properties → IPv4 → Advanced → WINS → Enable NetBIOS over TCP/IP (only if needed).
4. SMB version compatibility
   • TrueNAS supports SMBv2/3 by default; Windows 11 uses SMBv2/3. Don’t enable SMBv1 unless you know the NAS requires it — SMBv1 is insecure. If you must test SMBv1 temporarily: Turn Windows feature “SMB 1.0/CIFS File Sharing Support” on, test, then turn it off. Prefer fixing SMB2/3 or NAS settings instead. (See forum guidance on SMB mismatch fixes).
5. Firewall / antivirus / security software
   • Temporarily disable third‑party AV/firewall (or uninstallin Defender + firewall → enable File and Printer Sharing rules for Private networks.
   • If disabling fixes it, re-add explicit firewall rules for SMB ports (TCP 445, 139 and UDP 137–138) and SSDP if discovery is needed.
6. NIC driver / power / settings
   • In Device Manager → NIC → Properties → Power Management: uncheck “Allow the computer to turn off this device to save power.”
   • Advanced NIC settings: disable Energy‑Efficient Ethernet, Green Ethernet, Flow Control tweaks — sometimes EEE causes intermittent connectivity.
   • Try rolling back the driver or testing the vendor driver vs Microsoft driver.
   • Test with a static IP (temporarily) to rule out DHCP flakiness.
7. Router / multicast / IGMP / SSDP filtering
   • Some routers block multicast/SSDP which prevents discovery. Check router settings for IGMP snooping or multicast/filtering and temporarily disable those features.
   • If router has “AP isolation” or guest network features, ensure devices are on same LAN.
8. Clean boot / Safe Mode with Networking
   • Do a clean boot (disable non-Microsoft services/startups) and see if discovery works — this identifies third‑party interference.

If you still see intermittent web access (takes multiple tries to load a site)

• That points to a NIC or DNS issue: try alternate DNS (1.1.1.1 / 8.8.8.8) and test browsing.
• Run continuous ping to gateway and NAS while reproducing the issue: ping -t <gateway_ip>; ping -t <NAS_IP> to look for packet loss.

What to tell me next (so I can give a targeted fix)

• Does \<NAS_IP>\share open when you type it? If yes, that confirms discovery/name resolution problem.
• Any error codes when mapping (e.g., 0x80070035)?
• Is the PC wired or Wi‑Fi? NIC model (Device Manager → Network adapters → exact name).
• Output of ipconfig /all (paste the relevant lines) and whether other Windows machines can see the NAS reliably.

If you want, follow the diagnostic checks above and post the results (especially whether mapping by IP works and output of Get-SmbClientConfiguration / ipconfig /all). I’ll write the exact commands and registry tweaks needed next (SMB client tweaks, service auto‑start commands, hosts file entry, or NIC advanced settings) based on what you find.