Windows 10: Windows 10 Network Discovery Problem with Ubuntu/Samba Server

I have a problem that has me stumped. I have a Ubuntu Media Server (OS Version 14.04.1) running Samba 4.1.6. I have a Win 10 laptop (upgraded in August from 8.1) and Win 10 desktop (upgraded Jan 11th from Windows 7). The laptop doesn't (or very rarely) discovers the Samba shares. Windows sees the two other Windows PC's under the Network section. It doesn't seen to recognize the printer attached to the server. Print jobs seem to disappear into nowhere even though the printer is "there" under devices. It is also seen in Belarc Advisor. It does, however, always recognize the mapped drives of the 3 individual Samba shares on the server. It also discovers the Plex Media Server I have installed. It is under the Media Devices Section in Network. The desktop under both Win 7 and 10 discovers both the Network shares and the samba shares (and the network printer) connected to it as well as the Plex Media Server. I've attempted to match setting for setting from the desktop to the laptop (Advanced Sharing Options), but that hasn't solved the problem. Because it works on one system and not the other, I don't see where my Samba configuration is the problem. Anyone have any ideas?

:)

 

Windows 10 cannot browse my local network or see/connect to mapped drives

So I found a fix for this - The issue here is a Windows 10 machine that I log onto using a PIN, and trying to connect to shares on an Ubuntu/Linux SAMBA server

Go to Control Panel / Settings and search the Control Panel (top right) for "Credentials", click on the "Manage Windows Credentials" link

Then Add a Windows credential for the machine you are trying to connect to as follows:

Internet or network address: MACHINENAME

Username: WORKGROUP\USERNAME

Password: PASSWORD

replacing MACHINENAME, WORKGROUP etc. with your own values.

NB - For Username you must use the WORKGROUP or DOMAIN name of the machine you are trying to connect to (an Ubuntu Linux Samba server in my case) followed by the backslash followed by the username

Once you have done this, you can connect to \\MACHINENAME\SHARENAME using a mapped network drive or adding a "network location" to the share you are trying to connect to. I'm not sure if one is able to browse the server, but at least I can connect to my
shared data now.

Hope this saves someone some frustrating time when trying to connect from Windows 10 to a Linux Samba server.

 

Windows 10 cannot browse my local network or see/connect to mapped drives

I'm having the same issue here, and I can't find if anything has changed w.r.t. Samba/Lan Manager in Windows 10 that would prevent a Windows 10 machine (which does not belong to a "HomeGroup" cause I don't want to use "homegroups") from seeing other machines
on the network.

I have a very simple LAN at work with 2 Linux servers both running Samba that can browse each other using SMB fine, but the Windows 10 machine simply does not see any servers on the network (All are configured with the same WORKGROUP)

A Windows 7 machine can see the Linux servers

I have a Apple Mac on the network and it can browse the Linux Samba servers fine.

DNS etc. is all working fine. I can ping the server's IP address and their name, but cannot connect to any shares on the machines.

Most frustrating

 

There is a fix to disable SMB 2 & 3 on Windows. It is on a past thread and should be in the tutorials.

 

Tried one method - it didn't work. Then ran across this ongoing discussion at Microsoft: Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586 Used one of these - and viola! It works (for now) until the boys in Redmond hose it up again.

 

I wanted to blame M$ for it as well however after some research I found several servers were claiming to be Master Browsers. I logged on to those servers (yes Linux boxes) and set local master = no in the global confs and the rest of my network browse function worked.

The program I used to discover this was Scottie's LANscanner v1.63... You can run the tool and check your net. Thanks Scottie....