Windows 10: Windows 10 "silently" dropped support for Samba 3 domains?

Discus and support Windows 10 "silently" dropped support for Samba 3 domains? in Windows 10 Network and Sharing to solve the problem; After trying to join Windows 10 workstation to a Samba 3 domain, I finally found, after reading more of similar problems, that Windows 10, when asked... Discussion in 'Windows 10 Network and Sharing' started by Konstantin_Boyandin, Jul 19, 2018.

  1. Windows 10 "silently" dropped support for Samba 3 domains?


    After trying to join Windows 10 workstation to a Samba 3 domain, I finally found, after reading more of similar problems, that Windows 10, when asked to join the domain, indeed queries DNS only for the AD _ldap record for the domain.


    There was no explicit announcement about dropping Samba 3 domain (and Windows Server 2016 joined that domain without any problems) - only this subtle change that can be found only by trying.


    Can someone from Microsoft confirm that the NT domain support has indeed been officially dropped at or after version 1709 of Windows 10?

    :)
     
    Konstantin_Boyandin, Jul 19, 2018
    #1

  2. Setting up SAMBA

    For some reason my windows server will not connect to my linux server running centos6.3

    Here is what it does:


    Windows 10 "silently" dropped support for Samba 3 domains? screen%20cap.png


    and here is my samba share config

    Code: cat /etc/samba/smb.conf |less # Make sure not to do that on system directories as they may already have # been marked with othe SELinux labels. # # Use ls -ldZ /path to see which context a directory has # # Set labels only on directories you created! # To set a label use the following: chcon -t samba_share_t /path # # If you need to share a system created directory you can use one of the # following (read-only/read-write): # setsebool -P samba_export_all_ro on # or # setsebool -P samba_export_all_rw on # # If you want to run scripts (preexec/root prexec/print command/...) please # put them into the /var/lib/samba/scripts directory so that smbd will be # allowed to run them. # Make sure you COPY them and not MOVE them so that the right SELinux context # is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts # #-------------- # #======================= Global Settings ===================================== [global] # ----------------------- Network Related Options ------------------------- # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = HORSLEY server string = Samba Server Version %v netbios name = Mediaserver : ; interfaces = lo eth0 10.0.1.1/2 ; hosts allow = 127. 192.168.12. 192.168.13. # --------------------------- Logging Options ----------------------------- # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/log.%m # max 50KB per log file, then rotate max log size = 50 # ----------------------- Standalone Server Options ------------------------ # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. security = user passdb backend = tdbsam # ----------------------- Domain Members Options ------------------------ # # Security must be set to domain or ads # # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Use password server option only with security = server or if you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; security = domain ; passdb backend = tdbsam ; realm = MY_REALM ; password server = <NT-Server-Name> # ----------------------- Domain Controller Options ------------------------ # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job # # Domain Logons let Samba be a domain logon server for Windows workstations. # # Logon Scrpit let yuou specify a script to be run at login time on the client # You need to provide it in a share called NETLOGON # # Logon Path let you specify where user profiles are stored (UNC path) # # Various scripts can be used on a domain controller or stand-alone # machine to add or delete corresponding unix accounts # ; security = user ; passdb backend = tdbsam ; domain master = yes ; domain logons = yes # the login script name depends on the machine name ; logon script = %m.bat # the login script name depends on the unix user used ; logon script = %u.bat ; logon path = \\%L\Profiles\%u # disables profiles support by specifing an empty path ; logon path = ; add user script = /usr/sbin/useradd "%u" -n -g users ; add group script = /usr/sbin/groupadd "%g" ; add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /n ohome -s /bin/false "%u" ; delete user script = /usr/sbin/userdel "%u" ; delete user from group script = /usr/sbin/userdel "%u" "%g" ; delete group script = /usr/sbin/groupdel "%g" # ----------------------- Browser Control Options ---------------------------- # # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply # # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable # # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; local master = no ; os level = 33 ; preferred master = yes #----------------------------- Name Resolution ------------------------------- # Windows Internet Name Serving Support Section: # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both # # - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server # # - WINS Server: Tells the NMBD components of Samba to be a WINS Client # # - WINS Proxy: Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. # # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. ; wins support = yes ; wins server = w.x.y.z ; wins proxy = yes ; dns proxy = yes # --------------------------- Printing Options ----------------------------- # # Load Printers let you load automatically the list of printers rather # than setting them up individually # # Cups Options let you pass the cups libs custom options, setting it to raw # for example will let you use drivers on your Windows clients # # Printcap Name let you specify an alternative printcap file # # You can choose a non default printing system using the Printing option ; load printers = yes ; cups options = raw ; printcap name = /etc/printcap #obtain list of printers automatically on SystemV ; printcap name = lpstat ; printing = cups # --------------------------- Filesystem Options --------------------------- # # The following options can be uncommented if the filesystem supports # Extended Attributes and they are enabled (usually by the mount option # user_xattr). Thess options will let the admin store the DOS attributes # in an EA and make samba not mess with the permission bits. # # Note: these options can also be set just per share, setting them in global # makes them the default for all shares ; map archive = no ; map hidden = no ; map read only = no ; map system = no ; store dos attributes = yes #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes ; valid users = %S ; valid users = MYDOMAIN\%S ;[printers] ; comment = All Printers ; path = /var/spool/samba ; browseable = no ; guest ok = no ; writable = no ; printable = yes # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /var/lib/samba/netlogon ; guest ok = yes ; writable = no ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ; [Profiles] ; path = /var/lib/samba/profiles ; browseable = no ; guest ok = yes # A publicly accessible directory, but read only, except for people in # the "staff" group ; [public] ; comment = Public Stuff ; path = /home/samba ; public = yes ; writable = yes ; printable = no ; write list = +staff [Movies1] path = /Movies1 writeable = yes browseable = yes valid users = administrator [Movies2] path = /Movies2 writeable = yes browseable = yes valid users = administrator [Movies3] path = /Movies3 writeable = yes browseable = yes valid users = administrator [Movies4] commnet = Public Storage path = /Movies4 browseable = yes guest ok = yes writable = yes printable = no[/quote] What am I doing wrong? I've setup an administrator user ( I think) but it will not connect to the share, they show up but no access. Any ideas?
     
    freaksavior, Jul 19, 2018
    #2
  3. Monk.e83 Win User
    Unlocked Realtek HD Audio Drivers Windows 7 & 8 (With Dolby Digital Live and DTS Interactive)

    DTS supported natively by Windows 8/8.1 and it should work on windows 10 too just DDL require to unlock your driver .
     
    Monk.e83, Jul 19, 2018
    #3
  4. robos Win User

    Windows 10 "silently" dropped support for Samba 3 domains?

    Getting a domain name...

    Just simple 3 steps to make your website glow to millions…
    Step 1: Sign up now and get a FREE domain!
    Step 2: Design your new website in minutes!
    Step 3: You are live! Share your life online!

    Click here…
     
    robos, Jul 19, 2018
    #4
Thema:

Windows 10 "silently" dropped support for Samba 3 domains?

Loading...
  1. Windows 10 "silently" dropped support for Samba 3 domains? - Similar Threads - silently dropped support

  2. Is Microsoft Really Dropping Support For Windows 10 In 2025

    in Windows 10 Installation and Upgrade
    Is Microsoft Really Dropping Support For Windows 10 In 2025: Hi, I was searching through the web when I saw something that said “Microsoft Will Drop Support For Windows 10 On October, 14, 2025.Is this true? If so, how come this is happening?Is another windows coming out?...
  3. Windows 10 and Samba - Raspberry Pi 3

    in Windows 10 Network and Sharing
    Windows 10 and Samba - Raspberry Pi 3: I know everyone in this forum is probably sick of this scenario but I would still like the input if you have it. I have searched the forum and I see that this is a common problem which is more often than not blamed on Samba. Could be but ... I am using a Toshiba S75-A laptop...
  4. Windows 10 - no support for 3 monitors

    in Windows 10 Drivers and Hardware
    Windows 10 - no support for 3 monitors: This is the same question as on the following thread: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-with-3-monitors/7766e5db-d289-4a2c-af46-952577c45dd5 Has there been any resolution? My situation is the same as they described -...
  5. Windows - users logged on to samba NT domain cannot connect WIFI ! but local domain users can.

    in Windows 10 Network and Sharing
    Windows - users logged on to samba NT domain cannot connect WIFI ! but local domain users can.: hi everybody, The problem I'm experiencing is pretty much what is in the subject. ver. 1903 windows are members of Samba (classic NT) domain and users of that domain when logged in cannot connect to WIFI, but if a local user logs in on the same workstation then WIFI gets...
  6. 3 Applications Not Supported by Windows 10

    in Windows 10 Software and Apps
    3 Applications Not Supported by Windows 10: Hi Forum, I have 3 applications which are not supported by Windows 10 and no longer available. All 3 work in tangent and are dependant on each other to work successfully. Pitney Bowes...
  7. SAMBA and Windows 10

    in Windows 10 Virtualization
    SAMBA and Windows 10: Hi there I know a load of people have Linux as a VM on a Windows 10 Host (and the other way around too). Samba will often yield strange results with W10 if you don't set up the smb.conf file correctly to work with W10. This should also fix "timeout on server" type of...
  8. Safari support dropped

    in Browsers and Email
    Safari support dropped: This is old news, but I only learned it today. Apple has dropped support for its Windows version of the Safari browser, but has given little publicity to the decision. 47500
  9. Creating a samba share in windows 10

    in Windows 10 Network and Sharing
    Creating a samba share in windows 10: I've been using unauthenticated samba share on my computer for well over a decade using windows 7, vista, and XP (and maybe even further back) to network with various devices in another room via an ethernet cable. I believe Microsoft removed unauthenticated samba shares from...
  10. Acessing Windows 10 FROM Samba

    in Windows 10 Network and Sharing
    Acessing Windows 10 FROM Samba: Hi there Accessing shared W10 files from Samba sometimes cause problems such as Timeout on server or not being able to acess the files although entering a SMB:\\Ipaddress will usually work where IPADDRESS is the address of the Windows machine. In most cases (not Domain...