Hello,
In my home LAN, there is a Window 11 Pro 24H2 PC and a few old media players which only support NetBIOS and SMB 1.0 under Linux. Any of them, PC or player, can access all the others' shares if I manually provide the UNC names: \\ComputerName or \\DeviceName.
However, in terms of dicovering the devices, the players usually can see the PC, but the PC can never see the players.
On the Windows 11 PC, I have added "SMB 1.0/CIFS File Sharing Support" and enabled SMB 1.0 server and client. In Ethernet adapter settings, NetBIOS over TCP/IP is explicitly selected, i.e., not just Default. In Network Connection Details, it's yes for NetBIOS over TCP/IP.
Also, Network Discovery and File and Printer Sharing are turned on for the Private profile. The following services are all running (though the startup types of some are manual):
Computer Browser
Function Discovery Provider Host
Function Discovery Resource Publication
Server (Automatic
SSDP Discovery
TCP/IP NetBIOS Helper
Worktation
I have even tried creating Windows Defender Firewall inbound "Allow" rules for TCP/UDP port 137-139, 445.
But Windows 11 just can not discover those players.
Maybe Windows 11 (esp. 24H2) just doesn't want to use NetBIOS any more?
If so, can we force NetBIOS for Windows 11 in its discovery endeavor?
In my home LAN, there is a Window 11 Pro 24H2 PC and a few old media players which only support NetBIOS and SMB 1.0 under Linux. Any of them, PC or player, can access all the others' shares if I manually provide the UNC names: \\ComputerName or \\DeviceName.
However, in terms of dicovering the devices, the players usually can see the PC, but the PC can never see the players.
On the Windows 11 PC, I have added "SMB 1.0/CIFS File Sharing Support" and enabled SMB 1.0 server and client. In Ethernet adapter settings, NetBIOS over TCP/IP is explicitly selected, i.e., not just Default. In Network Connection Details, it's yes for NetBIOS over TCP/IP.
Also, Network Discovery and File and Printer Sharing are turned on for the Private profile. The following services are all running (though the startup types of some are manual):
Computer Browser
Function Discovery Provider Host
Function Discovery Resource Publication
Server (Automatic
SSDP Discovery
TCP/IP NetBIOS Helper
Worktation
I have even tried creating Windows Defender Firewall inbound "Allow" rules for TCP/UDP port 137-139, 445.
But Windows 11 just can not discover those players.
Maybe Windows 11 (esp. 24H2) just doesn't want to use NetBIOS any more?
If so, can we force NetBIOS for Windows 11 in its discovery endeavor?
Last edited:
My Computer
System One
-
- OS
- Windows 11 Pro 24H2 build 26100.4349
- Computer type
- PC/Desktop
- Manufacturer/Model
- self-built in Oct. 2024
- CPU
- Core i5-12600K
- Motherboard
- Gigabyte B760M GAMING X AX DDR4 v1.2
- Memory
- 2 x ADATA XPG GAMMIX D10 DDR4 16GB
- Graphics Card(s)
- (iGPU) Intel UHD Graphics 770
- Sound Card
- onboard Realtek ALC897 audio codec
- Monitor(s) Displays
- Chimei 22SH-L LCD (HDMI, DVI, D-Sub, 2010)
- Screen Resolution
- 1280 x 720
- Hard Drives
- 1 x WD_BLACK SN850X NVMe SSD 1TB
2 x WD WD5003ABYX RE4 500G SATA2 (RAID 0)
- PSU
- FSP HEXA 85+ HA350 350W
- Case
- Cooler Master N400
- Cooling
- DeepCool AG400 Plus tower cooler, 4 x PWM case fan
- Keyboard
- infotec INF-KB-S15
- Mouse
- Toshiba Pala-Chan
- Internet Speed
- 522/263 Mbps
- Browser
- MS Edge
- Antivirus
- Windows Defender
