Windows 10: Samba Shares don't show up in Windows 10 Network

Samba has kept up. It is Microsoft who is lagging behind. All versions of Samba are backwards compatible. Windows has never worked right with Samba as far back with XP, without doing the registry edit and changing the settings in Windows in Advance Sharing, to not use Homegroup, but the second choice.

Samba writes the code, along with others who contribute. But because Microsoft Sales wants to force everyone to use Sharepoint, etc. as their server product, even though a typical home user does not need a server.

It used to be with Samba 3.x.x, you had to use Capital letters for your username, no special characters or mix of upper and lower case letters. That was because Windows did not comprehend that info.

 

Hi there

I'm running CENTOS 7 -- no problem connecting to Windows from CENTOS - should work also on other distros

1) use smbpasswd to add your user - use the user you have on windows
2) in the GLOBAL settings of the samba config file get your netbiosname set correctly. note This is for HOME networks - I'm not using logon domains etc. simply computers on a home LAN.


[global]
workgroup = WORKGROUP
passdb backend = smbpasswd
preferred master = yes
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
usershare allow guests = Yes
server string = ""
usershare max shares = 100
usershare owner only = false
netbios name = gylfi
wins support = no
name resolve order = bcast host lmhosts wins

Now using Dolphin or whatever you'll be able to see the machines and just double click on the Windows machine. A login popup will be displayed - enter your (Windows) username and password and you'll have access to all the shares - ensure the drives / directories are shared.

The other way round - from Windows to Linux should be no problem provided you've added the shares in the rest of the samba configuration file.

Note also if you have a firewall enabled in Linux allow outbound and inbound connections for SAMBA ports. Same applies for Windows connections too. Check firewall settings.

Cheers
jimbo

 

I guess I'm having a conceptual problem with this "fix" of disabling smb2/smb3 in Windows.

I have an Ubuntu 14.04 machine with Samba at 4.1.6. Browsing for shares from Explorer does not work for me either but I can access the Ubuntu machine directly from Run ( Win Key + R ) with ( in my case ) a
Code: \\bart\Downloads[/quote] And the connection is made and I can access the share.

If I open the powershell as administrator and run Get-SmbConnection to get the details of this connection I get this:

Windows 10 is connecting to my samba server using version 3.0 of SMB.

I don't think this is a samba version problem I think it's a more complicated issue from this Function Discovery process that Explorer now uses to "browse for" or "discover" hosts on the network.

We got the attention of a Microsoft employee in this thread so one hopes it will eventually get fixed:
Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

 

I removed netbios from my samba file share,
added this to my smb.conf
disable netbios = yes
smb ports = 445
and can now connect with no problems using \\ip or \\hostname as long as you add the host name to your windows host file.

 

You don't even have to mess with a host file. Windows 10 has joined the 21st century and speaks mDNS / DNS-SD ( Avahi in Linux / Bonjour in OSX ).

You can access a Linux or OSX machine by it's hostname and a ".local" TLD. So in my example above I would access my Ubuntu machine with a:
Code: \\bart.local\Downloads[/quote] Not more netbios, workgroups, name resolve order changes, 15 character host name length restrictions, etc... It's also way faster at connecting.

The only thing Windows didn't do is take this to it's logical conclusion. Both OSX and Linux can "announce" to the network that they are a samba server using dns-sd. All other Linux and OSX machines will see them immediately under their respective Networks. Windows cannot do that - yet.

 

Not more netbios, workgroups, name resolve order changes, 15 character host name length restrictions, etc... It's also way faster at connecting.

The only thing Windows didn't do is take this to it's logical conclusion. Both OSX and Linux can "announce" to the network that they are a samba server using dns-sd. All other Linux and OSX machines will see them immediately under their respective Networks. Windows cannot do that - yet.[/quote] You seem to know these things. Perhaps you can help?
I have one Win10 x64, two Win7 x64, one OSX Captan and one WD MyCloud NAS connected to the network.
On Win10 x64 v10240 all c's could see each other and the NAS in the "networkbrowser", I could access all from all. Homegroup is disabled. After the Win10 x64 10586 upgrade the OSX and the NAS completely disappeared from the Win10 machine. I have managed to make the NAS flash by once by disabling and the enabling networkdiscovery on the Win10 machine. All shares are reachable by name. Can you help?

 

Build 10586 is when everything broke in Win10 Network discovery. I am like you. I can access everything on my network as long as I ask for it by name.

That is what this TechNet thread is about : Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

 

Ok, understand. Have you seen this http://answers.microsoft.com/en-us/w...864d59f?page=1
Look at Dusty Harpers post on Nov. 21.

 

No, but I will when I get a chance.

 

DoItJust, the WD MyClouds have been headaches for a lot of people. I use a Lenovo ix2-4 and have no problems with it.

 

Hi there.

Using Static IP's and Host names isn't a sensible answer -- too much maintenance etc.
Netbios simply works.

On Windows though some people report that one of the ports that used to be used in searching / retrieving data from the LAN should be disabled -- I can't remember if it was 445 or another one. This trick worked in earlier releases of W10 but AFAIK it isn't needed any more.

I used also to have a problem when accessing WINDOWS FROM LINUX is that even if you shared the whole "C" drive most of the "C" directory wasn't shown and not all files were listed.

Seems to work 100% these days.

It could be the versions of Linux you are using. CENTOS is based on RED HAT ENTERPRISE which is extremely widely used for networking so I'd expect CENTOS to work perfectly as a server (which it does).

Other distros which aren't based on existing commercial servers might not work so well -- you have to search the various 'Nix forums.

OPENSUSE might be another good one to try as it's also based on a commercial server too.

I'm actually quite surprised to find networking seems to be working as it should be in this release of Windows --must be a First for ms this time as windows networking has always been a dog ever since Windows first started using it !!.

Cheers
jimbo

 

Jimbo anything like printers, NAS, etc, get a Static IP on my network. Everything else gets a Dynamic IP.

 

Hi there

That's fine - I meant things like computers should have dynamic IP's.

Did you fix the Samba issue.

Try disabling firewalls (on all machines) while testing. Of course re-enable after you've got things working.

Cheers
jimbo

 

Thanks, but I can't buy new hw just because of this. And I can't throw away my Mac.

Four questions I really would like you guys who understand this give an anser to:
Why does it work in 10240 but not in 10586, a bug or a setting changed?
Why can I see my Nas when the air pressure is the right one? (I.e. sometimes)
What about my Mac, are Mac's also being a headache for a lot of people?
Best thing to do, continue looking for solution for 10586, wait for a MS fix or stay on 10240 forever?

 

I have not had any issues with 10586 on my wife's laptop. The samba config I use, works just fine with no issues.