Windows 10: Cannot browse WORKGROUP shares

I have a relatively simple network that consists of a couple Windows 10 PCs, Android devices and Raspberry Pis. For some reason I cannot access the shares provided by the PIs from anything but the android devices. It says they are in WORKGROUP (using Kodi) but they simply don't show up in the network browser under Windows 10. This used to work perfectly. Right now I have to use an android device to copy files from my windows PC to the PI share. Does anyone have any solutions to this?



:)

 

Windows 10 HomeGroup required?

Windows 10 is a pain when it comes to Home Networking! The simple task of connecting to a shared drive or folder seems impossible! Homegroups no longer work. The troubleshooter can't find anything wrong, yet I cannot connect any of four computers to the
homegroup after upgrading to Windows 10.

Even though all computers are in the same workgroup, I cannot browse them. The correct Username and Password is always wrong!

WHY Microsoft?

 

After the 1511 update, the windows 10 pc's cannot see other shares if it is not the master browser

Thanks for replying. Still the problem remains: the windows 10 machine cannot see all the shared pc's, only itself and a windows 7 pc. not even a windows server 2012r2 datacenter in workgroup mode(no domain). It has to be the MB to see all pcs and shares

 

Hey jglazer,
Can you still access the shares using ... \\RaspberryHostName\ShareName or \\RasperryIPaddress\ShareName
If so you can map the network shares ... Map Network Drive in Windows 10 Network Sharing Tutorials

FYI ... If your Win10 version is 1709 (Fall Creators Update) it could be that SMBv1 has been uninstalled ...

• Windows 10 Home and Windows 10 Professional no longer contain the SMBv1 server by default after a clean installation.
• Windows 10 Home and Windows 10 Professional still contain the SMBv1 client by default after a clean installation. If the SMBv1 client is not used for 15 days in total (excluding the computer being turned off), it automatically uninstalls itself.
• In-place upgrades and Insider flights of Windows 10 Home and Windows 10 Professional do not automatically remove SMB1 initially. If the SMBv1 client or server is not used for 15 days in total (excluding the time during which the computer is off), they each automatically uninstall themselves.
• Because the Computer Browser service relies on SMBv1, the service is uninstalled if the SMBv1 client or server is uninstalled. This means that Explorer Network can no longer display Windows computers through the legacy NetBIOS datagram browsing method.

Reference ... https://support.microsoft.com/en-us/...r-version-1709

 

I am using a linux version specific to Kodi on the Raspberry Pi. It support SMBv2 and v3 by default. I turned on v1 as well. The really odd thing is that I had a laptop that I took to my sister's to setup her Rapberry Pi and I saw its shares fine. The same laptop does NOT see the shares here.

I cannot hit the shares using \\pi\sharename.

Any more thoughts?

 

What version of Raspbian are you running on the Pi's? Post your Samba Config files from both Pi's. If they have the "Master" settings set to yes, that can cause them to not be able to be recognized by Windows. A out of the box install of Samba on the Pi, should let you see them.

 

I am not using Raspian. I am using the minimal LibreElec version. I can browse the shares with my android devices just fine.

 

We already know that. You need to re-read what I posted and post the answers to those questions, along with the Samba Config files from the Pi's. If you do not follow that info, then this topic will close at this point. Regardless of what OS that you are running, we need the information.

It is like taking your vehicle in for servicing and telling the mechanic that there is something wrong, but you have to use the vehicle and will not let them help diagnose what is going on.

 

It is like taking your vehicle in for servicing and telling the mechanic that there is something wrong, but you have to use the vehicle and will not let them help diagnose what is going on.[/QUOTE]

 

I want to add one more morsel of information: I have an old Windows 10 Home computer and I can see the PI shares without a hitch so its obviously an issue with Windows 10 Pro.