Edit SMB - Conf File Vi /etc/samba/smb - Conf: Server Max Protocol NT1
Edit SMB - Conf File Vi /etc/samba/smb - Conf: Server Max Protocol NT1
Samba PDC:
Hostname: server.vinsoft.local
IP Address: 192.168.43.50/24
smbd –V
smbclient –V
Vi /etc/samba/smb.conf
[global]
workgroup = VINSOFT
security = user
browseable = yes
writable = yes
[printers]
path = /var/spool/samba
printable = Yes
print ok = yes
browseable = No
[netlogon]
path = /var/lib/samba/netlogon
browseable = No
writable = No
[Profiles]
path = /var/lib/samba/profiles
writable = Yes
Create the shares with proper permissions which we have mentioned in the smb.conf file
Now, create the users whom you want to login to the domain.
useradd user1
useradd user2
Create Machine accounts:
“You need to create machine account for every machine in order to allow domain login from
Windows machines. The machine account are special accounts with $ at the end, i.e. machine$. The
system accounts for machines do not need login shell neither home directory.”
smbpasswd -m -a machine1$
Here, smbpasswd -m …. – tells that account will be used as NT primary domain controller (Machine
account)”
smbpasswd -a root
smbpasswd -a user1
smbpasswd -a user2
“Here, ‘root’ user is the administrator that can be used to join the Windows NT/2000/XP/7 systems
to be part of the domain. In this case, do not provide smbpasswd with the same password as the
actual root account on the server. Create a different password to be used solely for creating
computer accounts. This will reduce the possibility of compromising the root password.”
Finally start samba services and enable them to start automatically on every boot.
systemctl start smb
systemctl start nmb
systemctl enable smb
systemctl enable nmb
Firewall Configuration:
Samba uses the following Ports when runs as an Active Directory Domain
Controller:
Service Port protocol
DNS 53 tcp/udp
Kerberos 88 tcp/udp
firewall-cmd –reload
SELinux Configuration:
setsebool -P samba_domain_controller on
setsebool -P samba_enable_home_dirs on
Also to the Samab shares which we have defined in the smb.conf file.
chcon -t samba_share_t /var/lib/samba/netlogon
If you don’t want to mess up with Firewall and SELinux, simply disable them. Restart your server
once you completed all above steps.
WINDOWS 7
Don’t worry. We can easily fix this error by doing the following tricks.
To get rid of this error, open the windows registry. Go to HKEY_LOCAL_MACHINE -> SYSTEM ->
CurrentControlSet -> Services -> LanmanWorkstation -> Parameters.
WINDOWS 10
Windows 10: There Are Currently No Logon Servers Available to Service the Logon Request
After you successfully joined Windows 10 to your Samba NT4 domain, logging in failed and the
following error is displayed:
There are currently no logon servers available to service the logon request.
“This setting prevent all your clients to use a newer SMB protocol version than SMB1 when
communicating with the PDC. Anyway, the Samba team recommends to use this workaround.
Disabling newer SMB versions on the Windows 10 client instead prevent this machine
communicating using newer SMB version with all Samba/Windows hosts.”
Restart Samba
IMPORTANT: Registry Changes That You Should Never Set!
You must not to change the values of the RequireSignOrSeal or RequireStrongKey. Changing
the settings breaks the interoperability with Windows and Samba installations.
If you changed these parameters, reset the values of both keys back to 1:
[HKEY_LOCAL_MACHINE\System\CCS\Services\Netlogon\Parameters]
"RequireSignOrSeal"=dword:00000001
"RequireStrongKey"=dword:00000001