Linux SMB not showing up in File Explorer (but can be accessed direct)

jeffreywhunter · 17 Jan 2016

I'm on a WIndows 10 Pro PC accessing a linux server with samba etc installed and working well (visible via Homegroup to both Android and Windows 7 pro). From the Win 10 box, if I type the name of the server in Windows File Explorer, then the shares from the server show up without issue. However, if I go into the Network folder, it does not see the linux servers - even though they are correctly configured for the correct homegroup. My windows 7 machines can see the servers in "network" as can my android devices.

Here's a screenshot. Note, the red arrows show what displays in Network folder (red arrows). If I click on the Server Name (HunterNAS in this case), the server shares are displayed and it shows up in the Network folder (blue arrows). Even after making the successful connection, display of another file explorer window > Network folder displays no linux server shares...

Any ideas?

bro67 · 17 Jan 2016

You have to disable smb 2 & 3 in Windows 10. Microsoft is using the excuse that they made changes with those two protocols, to protect the OS. That is not the case.

jeffreywhunter · 17 Jan 2016

bro67 said:

You have to disable smb 2 & 3 in Windows 10. Microsoft is using the excuse that they made changes with those two protocols, to protect the OS. That is not the case.

Thanks for the idea. Gave it a try, but no luck... Ran the command, opened file explorer, navigate to network, do a refresh, no changes... According to the link you sent, a reboot is not required...

Linux SMB not showing up in File Explorer (but can be accessed direct)-20160118-kdus-78kb.jpg

jeffreywhunter · 17 Jan 2016

jeffreywhunter said:

Thanks for the idea. Gave it a try, but no luck... Ran the command, opened file explorer, navigate to network, do a refresh, no changes... According to the link you sent, a reboot is not required...

Just for grins, I rebooted to see if it made any difference. It did not...

Linux SMB not showing up in File Explorer (but can be accessed direct)-20160118-dmmf-144kb.jpg

bro67 · 18 Jan 2016

You have to disable the "Client" side on 10, then reaet Winsock and flush the DNS. That is the section that is missing, along with doing a reboot after you run all three options.

Someone can create a script that would allow you to chose Client or Server, enable or disable of SMB 2-3, and the flushdns, winsock reset with no problem.

The problem is getting people to trust the project that it is safe and will do exactly as stated that it is for.

jimbo45 · 18 Jan 2016

bro67 said:

You have to disable the "Client" side on 10, then reaet Winsock and flush the DNS. That is the section that is missing, along with doing a reboot after you run all three options.

Someone can create a script that would allow you to chose Client or Server, enable or disable of SMB 2-3, and the flushdns, winsock reset with no problem.

The problem is getting people to trust the project that it is safe and will do exactly as stated that it is for.

Hi there
the average person wouldn't have a clue of how to do this or even what it means.

Getting W10 to see Linux shares IS most definitely a problem as well as a lot of other issues with networking in general.

If I as a standard user want to browse a Home LAN via the network icon it should just work. I'm using DHCP so messing around with fixed IP addresses on the Lan and typing them in or fiddling around with a HOSTS file is not an answer either.

My Linux boxes just see ALL the computers on the LAN including the W10 ones so it should work in reverse too. My W7 and XP systems don't have the problem either.

Ms needs to get this thing FIXED ASAP -- if networking is broken then Ms need to go back to the drawing board again. Networking is definitely MAINSTREAM these days - very few homes don't use some sort of networking.

Cheers
jimbo

jeffreywhunter · 18 Jan 2016

bro67 said:

You have to disable the "Client" side on 10, then reaet Winsock and flush the DNS. That is the section that is missing, along with doing a reboot after you run all three options.

Someone can create a script that would allow you to chose Client or Server, enable or disable of SMB 2-3, and the flushdns, winsock reset with no problem.

The problem is getting people to trust the project that it is safe and will do exactly as stated that it is for.

Conceptually get what you're saying, but do not have the commands handy to disable the "client". I know how to reset winsock and flush the DNS. Do you have a script to do that or can you point me to directions? I have no problem building scripts, just need to know what the commands and syntax should be...

bro67 · 18 Jan 2016

The Powershell commands are most likely buried. I know that there is a tutorial out there. Here are the commands.

How to enable or disable SMB protocols on the SMB client
Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012

Note When you enable or disable SMBv2 in Windows 8 or in Windows Server 2012, SMBv3 is also enabled or disabled. This behavior occurs because these protocols share the same stack.
To disable SMBv1 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 start= disabled
To enable SMBv1 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto
To disable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
To enable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

Notes
You must run these commands at an elevated command prompt.
You must restart the computer after you make these changes.

bro67 · 18 Jan 2016

Jim the sad part is this goes back as far as Server 2008 and Windows 7. It has been the unseen thorn in everyone's side, because we all thought that it was a Linux problem with Samba, not the Windows side.

I have lost track from pulling out my hair, in having to look at it from the file server side, when all of the time Microsoft kept it quiet until Windows 10, when it became known that they were disabling SMB 2 & 3 connections from Linux for their own good.

This is why we have seen such a huge influx of people having issues with Media Servers, staying with 7, since it was a little less forgiving, except for large folders, when you try to browse them.

bro67 · 18 Jan 2016

Jim I have some things that are Static IP's. I am sure you have seen my network items. When I have had ATT & Comcast tech's come over for something. They are amazed that I have a SoHo network set up, when they are just expecting a single device and a few devices. It helps get the bad ones to allow me to introduce them to what they can expect from those of us that came from the Homebrew days and use our home networks to keep up with out skill sets.

The good ones look like the scenes on Willy Wonka and the Chocolate factory, when Willy sees the Golden Ticket. Eventually better is when you have a friend that you show your new ride and their eyes glaze over. Just have to nudge them after five minutes, to get to work.