Displaying 20 results from an estimated 500 matches similar to: "DsGetDomainControllerInfoW fails with level 2008+, works with 2003"
2012 Nov 21
1
Failure demoting 2008_R2 DC (S4rc5)
Hello,
We are currently testing S4rc5 for an upcoming S3 to S4 migration. I am
able to duplicate this issue with both classicupgrade and a new provision
(both cases using internal DNS). I am able to join a 2008R2 system to the
domain and promote it to a DC, however I am unable to demote it. The
problem appears to be that the 2008R2 server fails replicating to the S4
DC. The specific error that I
2013 Mar 20
1
Clients no longer updating DNS & unable to delete MX records
Hello,
After noticing some odd behavior on my domain, I realized that many of my
DNS records are incorrect and that clients are no longer properly updating
DNS. While looking into this, I also discovered that I am unable to delete
MX records via AD DNS Manager or samba-tool. Both tools "see" the record
but report it does not exist when I attempt to delete it. I can create new
MX
2015 Jun 12
3
Samba 4.1.17 Raise domain level to w2008 R2
Dear all,
My , samba-tool domain level show shows me it is W2003:
[root at s4master ~]# samba-tool domain level show
Domain and forest function level for domain 'DC=tplk,DC=loc'
Forest function level: (Windows) 2003
Domain function level: (Windows) 2003
Lowest function level of a DC: (Windows) 2008 R2
Can I raise without issues to W 2008 R2?
Or should I stay with 2003?
Greetings
2008 Aug 12
1
LNP Problems
What is the deal with "CSR's"?
TWTelecom is telling me that I can't port a number to their service
without a Customer Service Record. Apparently this is easy with
Verizon, and not so easy with some other companies.
Basically I'm at a brick wall with a couple of ports because TWTelecom
is telling me I HAVE to get a CSR and certain other providers (Time
Warner Cable for
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
J?en ai profit? pour desactive VPN et autre.
Du coup, je n?ai que :
root at TransmitCorp~# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 172.31.6.15 netmask 255.255.240.0 broadcast 172.31.15.255
inet6 fe80::bf:52ff:fe4a:fe3c prefixlen 64 scopeid 0x20<link>
ether 02:bf:52:4a:fe:3c txqueuelen 1000 (Ethernet)
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
?Ok, so now :
Content of /etc/hosts
127.0.0.1 localhost
172.31.6.15 adc1.transmitcorp.com adc1
Now, stop samba.
Cleanup current data and now setup samba and provision again.
cleanup /var/lib/samba /var/cache/samba
Rename smb.conf
Then provision again, the base is wrong so the AD-DB has wrong data.
>
> I removed smb.conf from /etc/samba
> un the interactive
2020 Feb 28
0
Samba AD - Different IP than the existing one assigned
Try this.
systemctl stop smbd nmbd winbind
systemctl disable smbd nmbd winbind
systemctl mask smbd nmbd winbind
systemctl unmask samba-ad-dc
systemctl enable samba-ad-dc
systemctl start samba-ad-dc
Reboot server.
Check again.
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Lionel Monchecourt via samba
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
Hi, Thanks for helping.
Answers in line :
Log.smbd :
[2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main)
server role = 'active directory domain controller' not compatible with running smbd standalone.
You should start 'samba' instead, and it will control starting smbd if required
Really big hint there, you are not starting
2012 Oct 11
3
Joining Samba RODC, NT_STATUS_NOT_SUPPORTED
Dear list users,
I have a problem when joining an Active Directory domain. In this
project we have one Main Dc in capital city and one read only dc in
one remote city.
We join to main DC succesfully. However, we can not join to local
Replicate (rodc14). We are using this method for winbind / squid ntlm
authentication purposes not a full samba server. ?nternet conection is
not fast and we have
2019 Sep 18
2
LDAP bind to AD fails
Am 18.09.19 um 19:16 schrieb Kris Lou via samba:
> More than likely, certificate issues.
>
> If you use the IP in pfsense, then the Samba certificate needs to have the
> IP as the CN.
So you suggest to contact the dc via hostname ...
googled this query command:
# openssl s_client -connect adc1:636
tells me ...
CONNECTED(00000003)
depth=0 O = Samba Administration, OU = Samba -
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
Hi Louis
Here we go for the output of the script
Collected config --- 2020-02-27-14:28 -----------
Hostname: adc1
DNS Domain:
FQDN: localhost
ipaddress: 172.31.6.15 172.17.0.1 172.18.0.1 172.19.0.1
-----------
Kerberos SRV _kerberos._tcp. record verified ok, sample output:
Server: 172.31.6.15
Address: 172.31.6.15#53
Non-authoritative answer:
*** Can't find
2020 Mar 05
3
DCs from 4.10.x to 4.11.x
upgrade one of 2 DCs from 4.10 to 4.11.6
seems to work, I wonder about these messages:
M?r 05 09:06:21 adc1 samba[4198]: task[dreplsrv][4198]: [2020/03/05
09:06:21.737684, 0]
../../source4/dsdb/repl/drepl_notify.c:353(dreplsrv_notify_check)
M?r 05 09:06:21 adc1 samba[4198]: task[dreplsrv][4198]:
dreplsrv_notify_check: Failed to load repsTo for
2013 Feb 15
2
BIND9_DLZ CNAME Records Not Resolving from Windows Workstations
Hello,
In an effort to get MX and CNAME records working, I have migrated from
Samba's internal DNS to bind9_dlz. I am now seeing strange behavior where
CNAME records resolve correctly on the S4 DC, but not from workstations.
Please see the case below where I have foo.internal.testdom.com aliased to
google.com using a CNAME record. I do not understand why this is occurring
This should work,
2005 Nov 03
1
Custom kernel always crashes
2019 Aug 30
2
backup AD content
On 30.08.19 11:01, Andrew Bartlett wrote:
> I'm very sorry to advise that this script is not race-free in the
> locking done on the AD databases, which is why we have written the
> 'samba-tool domain backup offline' tool which holds the correct locks.
>
> You should only need to back up the domain on one DC as long as you are
> confident the DC is correctly
2014 Jan 15
1
Samba 4.0.9 running on centos 6.5 (64bit) share access issues
Hi,
We are running Samba 4.0.9 running on centos 6.5 (64bit) with SecureLinux disabled.
Having some share access issues, what are we missing to solve this puzzle?
We are attempting to get the MSDFS share working. Until we can fix this we cannot continue.
This is the Domain provision and dns, and reverse zone setup.
Dhcp server set point all clients at samba as primary dns server.
Nslookup
2008 Sep 04
3
Samba server as part of AD domain keeps asking for username and password
Hello all,
I'm trying to set up my samba server rev 3.2.3 on opensuse 10.3 as a
member of the active directory domain, so that client connections can be
authenticated by the AD server. Unfortunately when I try to connect to
the samba server from a windows XP system, it keeps on asking me for
user name and password.
I've been reading through various howto's and descriptions but no
2013 Jan 31
2
Samba4 Internal DNS - CNAME not working
Hello,
It seems Samba4 is having problems with CNAME records. I am seeing the same
behavior as mentioned in the thread below. Is there any ETA on a fix for
this? This is identical to the problem with MX records. This is currently a
much bigger problem than the MX records. I appreciate any assistance.
[root at DC1 var]# dig autodiscover.testdom.com CNAME
; <<>> DiG
2020 Feb 20
0
Unable to get primary group information when using AD authentication with samba-4.10.4
'wbinfo -a' is basically the same as logging in, but you should be able
to get a users primary group without the user logging in, this will
depend on what you mean by 'primary group'. On Windows, every users
primary group is 'Domain Users' and when you make a Unix computer a
domain member, Unix users get the same primary group by default. Before
Samba 4.6.0 there was
2003 Nov 21
1
Winbindd and SSH (just disconnects after login)
It looks like I've gotten the majority of things working in regards to
Winbind. Users are being authenticated by the NT4 PDC when connecting to
shares, but I can't seem to get things set up correctly to allow logging in
via SSH(OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090702f). It
appears as though I'm successfully authenticated by the PDC, but then the
connection is