search for: nameserver3

Displaying 4 results from an estimated 4 matches for "nameserver3".

Did you mean: nameserver
2003 Feb 11
0
Vmware and samba
...nds before retrying DNS request. timeout = 2 # Retries before giving up on DNS request retries = 3 # Automatically detect the DNS servers (not supported in Windows NT) autodetect = 1 # List of DNS servers to use. Up to three may be specified #nameserver1 = 208.23.14.2 #nameserver2 = 63.93.12.3 #nameserver3 = 208.23.14.4 [netbios] # This section applies only to Windows. # Timeout for NBNS queries. nbnsTimeout = 2 # Number of retries for each NBNS query. nbnsRetries = 3 # Timeout for NBDS queries. nbdsTimeout = 3 [incomingtcp] # Use these with care - anyone can enter into your virtual machine thro...
2017 Dec 11
0
DNS issue with clean install of samba 4.5.12-Debian
...ubusercontent.com/thctlo/samba4/master/samba-setup-checkup.sh You can wget this one directly. You should see ( my sample output ) sudo bash samba-setup-checkup.sh Check hostnames : Ok Checking detected host ipnumbers from resolv.conf and default gateway Ping gateway ip : 192.168.1.1 : Ok ping nameserver3: 8.8.8.8 : Ok Check ping google dns : 8.8.8.8 : Ok Checking file owner.. -rw-r--r-- root root /etc/samba/smb.conf Checking file owner.. -rw-r--r-- root root /etc/samba/lmhosts Checking file owner.. Missing file /etc/samba/smbpasswd drwxr-xr-x root root /usr/bin drwxr-xr-x root root...
2017 Dec 11
4
DNS issue with clean install of samba 4.5.12-Debian
On 12/8/2017 2:54 PM, Taylor Hammerling via samba wrote: > Glad you guys replied, here is my output :D > > root at dc1:~# ./samba-setup-checkup.sh > Check hostnames : Ok > ./samba-setup-checkup.sh: line 89: [: too many arguments > Checking detected host ipnumbers from resolv.conf and default gateway > Ping gateway ip : 172.28.0.1 : Ok > ping nameserver1: 172.28.255.49 : Ok
2018 Dec 20
5
Samba AD DC replication error - 2, 'WERR_BADFILE'
Hello everyone, I have setup two Samba AD DC's with BIND9_DLZ dns backend. faiserver.example.corp is one of them hosting all FSMO Roles. location-000001.example.corp is the second one. Both are in different subnets but can reach each other. Unfortunately replication only works from faiserver.example.corp -> location-000001.example.corp. In the other direction location-000001.example.corp