Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Windows 10 Samba Network Discovery Problem

  • Please log in to reply
1 reply to this topic

#1 mosscomes


  • Members
  • 21 posts
  • Local time:11:22 AM

Posted 12 January 2016 - 02:14 PM

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 yesterday 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 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?

BC AdBot (Login to Remove)


#2 Rikairchy


  • Members
  • 4 posts
  • Local time:11:22 AM

Posted 14 January 2016 - 04:35 AM

I came across this issue while joining a Windows 10 Pro workstation to a domain. Shares refused to properly respond, I had issues mapping, and share directories were not responding appropriately.


I fixed this issue by deactivating the CIFS/SAMBA feature in Programs and Features, restarting, enabling the CIFS/SAMBA feature again, and restarting once more. 

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users