- #Win 10 bonjour browser install#
- #Win 10 bonjour browser upgrade#
- #Win 10 bonjour browser windows 10#
- #Win 10 bonjour browser android#
My Web searches indicated that many people cannot see SMB shares in File Explorer either but can access a share by entering the UNC address in the File Explorer address bar.
#Win 10 bonjour browser windows 10#
When I first booted Windows 10 Enterprise 1709, SMB shares on my Linux machines were not displayed in File Explorer, and Windows 10 could not find them if I entered the UNC (Universal Naming Convention) address ‘ \\hostname\foldername‘ or ‘ \\IPaddress\foldername‘ (e.g.
#Win 10 bonjour browser install#
In other words, the Linux machines use SMBv3 with each other but SMBv2 with the phone (see my comments in the Comments section of my 2016 post ‘ A correct method of configuring Samba for browsing SMB shares in a home network‘).Īnyway, I happen to have an evaluation copy of Windows 10 Enterprise Version 1709 installed in a VirtualBox VM (virtual machine) on one of my Linux laptops and, purely to satisfy my curiosity, I decided to try to get Windows 10 Version 1709 to browse and access SMB shares on the Linux machines in my home network, and vice versa, without having to dispense with broadcast NetBIOS name resolution for the Linux machines and without having to install SMBv1 (and Computer Browser service) in Windows 10.
#Win 10 bonjour browser android#
Subsequently I found that Android 9 on my Samsung Galaxy Note 8 phone apparently does not support SMBv3, only SMBv1 and SMBv2, so I reconfigured Samba on my Linux machines to allow SMBv2 as well as SMBv3. SMBv1 is an inherently insecure protocol, so, after I dropped Windows, I reconfigured Samba on my Linux machines to use only SMBv3, which works fine. Prevent Linux firewalls interfering with Samba commands in a home network that uses broadcast NetBIOS name resolution.A correct method of configuring Samba for browsing SMB shares in a home network.One of the machines in the network had Windinstalled, but that was replaced with Lubuntu in 2018. Two of my blog posts from 20 explain how I set up my home network for file sharing. The File Manager + app on my phone running Android 9 can also browse SMB shares on the Linux machines and create/copy/move/delete remote files and folders. All my machines can browse each other’s SMB shares and create/copy/move/delete remote files and folders. Of course I know that NetBIOS - especially broadcast NetBIOS for name resolution - is ancient networking technology, but it works well for my home networking needs. Since then my home network has comprised a server, desktop and laptops running various Linux distributions with Samba and using broadcast NetBIOS for name resolution. None of that interested me since I stopped using Windows 10 after Version 1607. To put it another way, if you install SMBv1 in Windows 10 you automatically install Computer Browser service as well. Thus, as SMBv1 is not installed by default in Windows 10 Version 1709 and later versions, neither is Computer Browser service. Microsoft could have provided them separately, but it made some sense to bundle them together in the early days of Windows networking.
SMB has not been dropped, though Versions 2 and 3 of the SMB protocol are now used, albeit using a different mechanism for device discovery.Īlthough they perform different jobs, Microsoft bundled the Computer Browser service software with the SMBv1 software. Thus Microsoft has dropped the concepts of network ‘workgroups’, ‘master browsers’, NetBIOS, NetBIOS broadcasts, WINS and so on. Computer Browser service used NetBIOS and SMBv1 to provide what Microsoft named ‘ My Network Places‘ or ‘Network Neighborhood’. Nevertheless I am aware that, since Version 1709, Windows 10 no longer has SMBv1 and Computer Browser service installed by default.
#Win 10 bonjour browser upgrade#
I have not used Windows 10 for more than two years now (see ‘ Bye bye Windows 10, and good riddance‘ regarding my failed attempts to upgrade Windows 10 Version 1607 to 17).