[Samba] Samba 4 As PDC Not Populated In Windows Network

[zvonar at mediprogress.eu]

Dear Sirs,

I have been given your e-mail address by Jeremy Allison. I would like to submit the following issue I have. You should also know I have been searching Internet for articles before and found that the behavior I wish you to help me with is quite common. The issue is the Samba 4 server integration into a Microsoft Windows network. I have done this and that configuration as particular contributors advised in forums and other Internet articles. But still there is no success. My problem is how Samba 4 server as PDC must properly be configured so that it populates itself in the Windows network as other Microsoft Windows computers correctly do. I have not been able to see the Samba server in the network list even though the network discovery was allowed on Windows workstations and their firewall was disabled temporarily. To access the shares on Samba with \\server_name\share_name, or \\samba_server_ip_address\share_name, or through mapped network drives is working perfectly, however. Here are details I suppose you should know to be able to consider what might be wrong:
  1.. OS of the box with Samba – Ubuntu Server 14.04.1 LTS 64-bit 
  2.. Samba version – 4.1.11 
  3.. Samba implementation – active directory domain controller 
  4.. How samba was installed – see this guide at http://www.youtube.com/watch?v=Rf7Hk8qWt1Q 
  5.. Other PCs on the LAN – Windows 8.1, Windows 7
Please be kind enough and explain shortly, if the Samba Server version 4.1.11 as PDC could populate itself in the Microsoft Windows network at all, so that it can be accessed through network discovery rather than through mapped drives and/or with \\server_name\share_name, or \\samba_server_ip_address\share_name, or point me out to the right guide/article in Internet about how to achieve my goal.

Many thanks for your nice support in advance.


Jozef