Displaying 20 results from an estimated 20000 matches similar to: "high cpu usage samba 4 AD"
2018 Feb 13
2
high cpu usage samba 4 AD
Hi,
First of all thanks for your answer, today has increased cpu usage,
only change is add a new group with 3500 users, It could be the
problem?
a last question, now we only have one dc, no replication.
If we add another dc will increase performance and will be a
loadbalance the load?
Now I can't upgrade to 4.7, I have to shcedule an upgrade and
make test, any suggestion or a workaround?
2018 Feb 13
2
high cpu usage samba 4 AD
OK, Thanks for your information.
If I remove this new group with 3500 users, I understand that load
will be recovered to normal usage, correct?
About upgrade if I have only one server with 4.4.5 the best option is
add another dc with 4.7 compiled, then transfer and upgrade (or join
old server) or upgrade actual 4.4.5 to 4.7 and then add a new dc?
I like to keep 2 dc with same config and fully
2018 Feb 13
0
high cpu usage samba 4 AD
On Tue, 2018-02-13 at 23:31 +0100, Trenta sis wrote:
> Hi,
>
> First of all thanks for your answer, today has increased cpu usage,
> only change is add a new group with 3500 users, It could be the
> problem?
Yes, that will do it. This is exactly the use case we have been
working to make perform well since Samba 4.5, with Samba 4.7 having the
best behaviour so far.
> a last
2019 Sep 17
3
Samba 4.4 AD DC and GET_ANC restriction from Samba 4.5 DC joining (was: Re: Error join samba 4.10.7 to samba 4.4.5)
Hi,
About duplicate issues warning during join, What I can do to find and
solve this errors?
I like to investigate source of this issue and solve this errors before join
Thanks
Missatge de Trenta sis <trenta.sis at gmail.com> del dia dt., 10 de set.
2019 a les 11:14:
>
> Hi,
>
> About duplicate issues warning during join, What I can do to find and
> solve this errors?
>
2019 Sep 12
5
Questions about samba upgrade
Hi,
I'm making tests to migrate our actual 4.4.5 to a latest versions and
add a second dc.
I have added a second dc with 4.10.7 and seems to work fine, now I
have 4.4.5 with fsmo roles and a second dn with 4.10.7, but reading
wiki https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC seems
that since latest days some changes about steps to upgrade, now seems
that is recommended to us
2018 Feb 12
3
domain users issue
Hi,
If you try net group /domain "Domain Users" in samba domain with
domain users as primary group any user is showed, but If you try the
same in a native AD then users are listed, try this to reproduce the
error
Thanks
2018-02-12 20:24 GMT+01:00 Trenta sis <trenta.sis at gmail.com>:
> Hi Rowland,
>
> Not really sure if that is correct, tried with native AD and domain
2019 Sep 19
1
Duplicate attribute value warnings from ldb
On Thu, 2019-09-19 at 09:49 +0200, Trenta sis via samba wrote:
> hi
> Sorry, error is
>
> ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in
> CN=server,OU=servers,DC=DOMIAN,DC=COM for index on
> servicePrincipalNAme, duplicate og objectGUID
> 931a3f57-1062-423e-9488-695700b197b0 in
> @INDEX:SERVICEPRINCIPALNAME:WSMAN/OLD-SERVER
>
> multiple errors liek
2018 Feb 12
2
domain users issue
Not possible, I do not have a Windows AD DC, but I don't doubt it
works, probably because windows has a similar work around to
'samba-tool group listmembers Domain\ Users' --> Correct this command
returns correctly the users
Can you create a file on the netapp that ends up belonging to
'username:Domain Users' ? --> Correct fiel created without issues
Does 'getent
2016 Sep 14
3
Security event log in samba 4.4.5 domain controller
Hi,
I have samba 4.4.5 configured as AD wortking correctly, now I need to
configure Mcafee Logon Collector to receive security event about user
login, this application requires to read security event log about domain
controller
I have tried to connecto to doamin controller form windows server with
connect as and view event log but any event viewer is showed...
I have tried to configure
2019 Sep 19
4
Error demote
Hi,
during a demote of an online and working DC I receive this error
dsreplicasync failed (8440 'werr_ds_dra_bad_nc')
Any suggestion where could be the issue, server is not really demoted
Server is samba 4.4.5 and other server that has fsmo roles is 4.10.7
Thanks
2016 Oct 30
3
Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5
Hi,
I'll try to give information asked in preious messages:
- We have only one samba Domain controller and one dns (bind in same samba
server)
- Our domain doesn't have any .local
- avahi is not running and we use debian lenny
- This is a samba 4 AD domain, migrated form samba 3 nt domain using
classic upgrade as it is described in samba wiki
- problem is reported in lan network, is not a
2019 Sep 09
2
Samba 4.4 AD DC and GET_ANC restriction from Samba 4.5 DC joining (was: Re: Error join samba 4.10.7 to samba 4.4.5)
Hi Andrew,
thanks for you information, but I have some question, I'm not a samba
expert... Sorry!
Not that issue, but a very well known one.
The trouble is, Samba 4.4 was happy to get a tree like this:
X
| |
Y Z
in an order like this:
Step 1
Y
Step 2
Y Z
Step 3
X
| |
Y Z
As long as everything worked out in the end, it was fine. But this had
issues, so we patched it to instead
2019 Apr 16
4
Samba supported TLS versions
Hi,
I have searched and not found waht tls versions are supported with
samba 4.4.5 as AD. IS tls 1.2 supported with samba 4.4? If not what
version?
Thanks
2019 Sep 05
1
Questions about 2n dc and samba update
Thanks Rowland!!!
Missatge de Trenta sis <trenta.sis at gmail.com> del dia dj., 5 de set.
2019 a les 11:52:
>
> Hi,
>
> Thanks for your information about DNS config.
> About second server and update, I understand that First I have to
> transfer role to new added, demote old, and then rejoin and transfer
> fsmo roles to source server, right?
> My question is related
2019 Sep 05
4
Questions about 2n dc and samba update
Hi,
I have to upgrade 2 different samba AD DC (2 domains) from 4.4.5 to 4.10.7
First is a single server and updaded with in-place upgrade from 4.4.5
to 4.10.7 and all perfect
Second environment I need to add a second dc and also upgrade existing
server, and I have some question about how to do this:
- join second domain server with 4.10.7
- then make in place upgrade on existing server dc1?
2019 Sep 23
3
testparm comaprison
Hi,
Thanks, Well winbind enum is needed, and ntlm auth is required by some
applications, seems that samba has disabled by default but windows has
enabled, we have to migrate some old applications
I understand taht is OK with yout comments
thanks
Missatge de Trenta sis <trenta.sis at gmail.com> del dia dl., 23 de set.
2019 a les 11:22:
>
> Hi,
>
> I have used testparm.
>
2016 Oct 27
2
Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5
hi rowland,
after migration one of past migration tasks were generare reverse zone and
add alla and ptr manually.
I have made some additional tests and seemsthat if we shutdown samba domain
controller or disconnect network then we can access with \\ip with two
domain members server, and then if we reconnect network in samba ad server
we reproduces error with \\ip
any solution?
thanks
2016 Oct 26
3
Can't access to \\ip and some cname after migration from samba 3 to samba 4.4.5
Hi,
Recently we have migrated from samba 3 nt domain to samba 4 AD (4.4.5) and
we have detected that some applications are not working correctly, this
applications need to access to \\ip resource, with name works, but we have
some applications that needs to work only by ip
Also detected this problem with some cname in dns are not responding we use
bind9 + dlz, and we if we access from \\name
2019 Sep 23
4
testparm comaprison
Hi,
Recently we have added 4.10.7 as additional dc, to our existing 4.4.5
samba AD DC, comparing output testparm I have detected that 4.4.5 has
map readonly = no
store dos attributes = Yes
but 4.10.7 doesn't have
Also compared smb.conf and both has the same configuration.
Is this correct? Are required this configurations on 4.10.7?
In a few day I want to upgrade this 4.4.5
2018 Feb 12
4
domain users issue
Hi,
Using a samba 4, and having users configured as primary group domain
users (513) we detected that then if you execute net group /domain
"Domain Users" then user is not showed in as member of domain users,
if you remove from primary group and assign another group then with
net group /domain "Domain Users" you can list this user as member.
This generates that for example