How to set up the work of "Network Neighborhood" in AD?

Question

linux

Good afternoon, how to set up the work of "Network Neighborhood" in AD? How to do it right.
In some shaggy year there were constant problems with master browsers, I solved the problem by installing samba + wins on debian (registered for each computer) and overestimated the priority for choosing a master browser. From that moment on, the network environment worked perfectly.
Now there is a task on introduction of computers in the domain.
Created by ad, dns, dhcp (on micro), wins (distributed via dhcp. Raised on Windows, removed from debian).
Started several departments in AD. Computers on the same local network, on the same subnet.
Without changing samba configs etc. from computers outside the domain in the network environment, all computers, from computers in the domain, only a small part, and not even some that are in AD. Everyone is visible from the domain controller.
From the tried:
1. disabled samba on debian, disabled everything except one / two PCs and the server through the registry

reg DELETE "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v "IsDomainMaster" /f
reg DELETE "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v "MaintainServerList" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v "IsDomainMaster" /t REG_SZ /d "FALSE"
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v "MaintainServerList" /t REG_SZ /d "No"

The server became a master browser, but there was no full network on the PC either in the domain or outside it.
2. I tried to edit the samba config, to change the workgroup to ad, and to this and that. (Probably did not do it right).

ps About DFS came across, read. While the networked environment interests.

samba config:

#======================= Global Settings =======================
[global]
  client max protocol = SMB2
  default = global
  max log size = 1000
  log file = /var/log/samba/log.%m
  passwd program = /usr/bin/passwd %u
  passdb backend = tdbsam
  unix charset = UTF8
  dos charset = cp866
  preferred master = yes
  netbios name = Debian
  map to guest = bad user
  obey pam restrictions = yes
  name resolve order = wins lmhosts bcast
  server role = standalone server
  unix password sync = yes
  workgroup = LAMBADA
  os level = 255
  wins server = ip_adres_wins_server
  server min protocol = NT1
  pam password change = yes
  usershare allow guests = yes
  panic action = /usr/share/samba/panic-action %d
  local master = yes
  dns proxy = no
  passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
  display charset = UTF8
  syslog = 0


#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0700



[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700


[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no



[share]
  path = /samba/share

Answer 1

Network Neighborhood is dead. And no one wants to revive him. It just died. It does not work even in win-only multi-segment networks, where there is a screw AD in the center, on which wins is installed. It seems that wins support has been cut out for nothing. Because the IP wins of the server is transmitted, registration in it goes ... but ... Windows (workstation) just don't give a shit about it. :( It stupidly shows only the local network segment and that's it.

Answer 2

The problem is in planning, not in how to enable the "network place"
Users' computers should not have resources that are available to others. This is the lot of file servers located in a separate subnet.
If you have an AD, then there is a GPO to throw labels or network drives to people as needed. There is no need for a networked environment right now.

Answer 3

Yes. on WINS the microsoft already hammered a bolt.
no official end-of-support message yet, but here's what it says in docs.microsoft.com
If you haven't deployed WINS on your network yet, don't deploy a WINS server by deploying a Domain Name System (DNS). The DNS service also provides computer name registration and resolution services and includes many additional benefits over WINS, such as integration with Active Directory Domain Services.