Displaying 20 results from an estimated 11000 matches similar to: "after classicupgrade"
2016 Jun 17
5
can't connect ldapsearch with samba 4
Hi,
I'm trying to migrate samba 3 NT domain to samba 4 AD, we have migrated
data and it seems correct, but now we need to connect with ldapsearch but
always receive errors like
ldap_bind: Strong(er) authentication required (8)
additional info: BindSimple: Transport encryption required.
command used is
/usr/bin/ldapsearch -H ldap://server -x -LLL -z 0 -D
2016 Aug 03
5
Samba 4.2.14 Group Policy (GPO) sync error
Can you run on a failing computer :
- netdom verify yourpcname
- nslookup yourpcname
All ok?
And is time in sync?
Did you install winbind after the update and also and did you change you server services line?
Like, i use bind9 dns
My smb.conf contains only this : server services = -dns
The full line is :
samba-tool testparm -vv | grep "server service"
2016 Jul 08
5
Samba update to 4.2.14 (SERNET) breaks LDAP access
Last night we updated out Samba-4 AD server to version 4.2.14 usng the SERNEt packages, running on SLES 12. We have a number of services (mail services, MANTIS, etc) that access the server via the LDAP interface and in all cases we discovered that none of them where able to establish a successful LDAP connection after the upgrade.
Previously we used plain LDAP to access the server, i.e. we did
2020 Oct 10
10
Mail samba
Hi I am trying to authenticate my mail server with samba ad.
The only problem is that I don?t get it working.
root at dna:/data/CA/EasyRSA-v3.0.6# ldapsearch -x -h gaia.rompen.lokaal -D 'vmail' -W -b 'cn=users,dc=rompen,dc=lokaal'
Enter LDAP Password:
ldap_bind: Strong(er) authentication required (8)
additional info: BindSimple: Transport encryption required.
I can not read
2018 Nov 05
2
classicupgrade
On Mon, 5 Nov 2018 10:28:31 +0100
Corrado Ravinetto via samba <samba at lists.samba.org> wrote:
> Hello
>
> Il 31/10/2018 17:35, Corrado Ravinetto via samba ha scritto:
> > ok, sorry, are all AD users
> i taked out id map in smb.conf, but when i connect with a client in
> log.smbd:
>
> [2018/11/05 10:20:29.489762, 0]
>
2016 Jun 20
1
can't connect ldapsearch with samba 4
Hi,
solved only making this changes :
in /etc/ldap/ldap.conf
add
TLS_CACERT /etc/ldap/ca.pem.crt
sample query with ldaps
# ldapsearch -H ldaps://server -x -LLL -z 0 -D
"CN=user,CN=Users,DC=domain,DC=com" -w "p" -b "CN=Users,DC=domain,DC=com"
Solved!
Thanks
2016-06-19 18:55 GMT+02:00 Trenta sis <trenta.sis at gmail.com>:
> Hi,
>
> First of all
2015 Jul 09
1
classicupgrade
Hi,
I have Samba3 domain, and I test the upgrade process to Samba4 AD (Samba
3.6.6->4.1.17). After classicupgrade I found a problem. I created a test
file, and wanted to change its group with chown "xy:Domain Users" testfile.
I got an error message: invalid group: "xy:Domain Users" (I think, because
the message was localised).
chown xy testfile works.
I had old files with
2015 Nov 03
4
ssh authentication with AD
This seems to be common thread on the list, but I'm pulling my hair out and
have to ask..
I've been following a couple of guides and using AD to authenticate users
on my linux system. These include the ubuntu guide --
https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
- https://wiki.samba.org/index.php/Setup_Samba_as_an_AD_Domain_Member
-
2020 Jul 15
2
Ubuntu 18.04 classicupgrade help
On Wednesday, July 15, 2020, 02:50:09 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
On 15/07/2020 19:26, Carl Hunter via samba wrote:
>? On Wednesday, July 15, 2020, 03:16:00 a.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
>?
>?
>? On 15/07/2020 01:14, Carl Hunter via samba wrote:
>> I've currently got a Ubuntu
2018 Sep 05
3
Authenticating against Samba 4 AD LDAP service
Hello,
One of Samba 3 -> Samba 4 migration task I am solving is changing
authentication against new Samba 4 AD domain.
Existing services use LDAP directory of Samba 3 to authenticate. The
simplest way to go would be just to replace LDAP credentials; however, I
don't quite understand which LDAP credentials to use/how to create them
for Samba 4 AD.
Sample command against Samba 4 LDAP
2020 Jul 15
2
Ubuntu 18.04 classicupgrade help
On Wednesday, July 15, 2020, 03:16:00 a.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
On 15/07/2020 01:14, Carl Hunter via samba wrote:
> I've currently got a Ubuntu 18.04 server running Samba?4.7.6 with an NT4 domain that I'd like to migrate to an AD.? I've found the following link but am struggling to match up the steps with the Ubuntu install.
>
2009 Aug 31
3
default profile
Hi,
I installed a SaMBa PDC and a BDC. When I log in to an XP client with a new
user, sometimes I get the initial profile settings from the netlogon share,
but often from local. When I get the local default settings, it is not
syncronized to the server at logout. Even if I get the new profile from the
server, on the same client, next time, with a new user, I get the new
profile from local. I
2020 Jul 15
2
Ubuntu 18.04 classicupgrade help
On Wednesday, July 15, 2020, 03:29:57 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
On 15/07/2020 20:13, Carl Hunter via samba wrote:
>? On Wednesday, July 15, 2020, 02:50:09 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
>?
>?
>? On 15/07/2020 19:26, Carl Hunter via samba wrote:
>>? ? On Wednesday, July 15, 2020,
2016 Oct 31
2
Samba 4.5 y opensuse42.1
Hi,
The ldapsearch message is because you can't connect by plain text (-x) by default .
Try using https, that should do it.
Does smbclient -L SERVERDOM -U Administrator work? Or does it give
NT_STATUS_LOGON_FAILURE as well?
if you increase the log level, do you see "Unable to convert SID (S-1-X-XXX) at index
X in user token to a GID." in your log files?
Em
2020 Jul 16
2
Ubuntu 18.04 classicupgrade help
On Wednesday, July 15, 2020, 05:03:52 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
On 15/07/2020 21:53, Carl Hunter via samba wrote:
>? On Wednesday, July 15, 2020, 03:29:57 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
>?
>?
>? On 15/07/2020 20:13, Carl Hunter via samba wrote:
>>? ? On Wednesday, July 15, 2020,
2016 Aug 11
1
after classicupgrade
Your lucky man,
I always to it, because i notices it somethimes didnt tot it automaticly,
and running it does not hurt.
That somethimes happens when you install/remove/install again.
Gr.
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rowland Penny via
> samba
> Verzonden: donderdag 11 augustus 2016 11:41
> Aan: samba
2020 Jul 16
2
Ubuntu 18.04 classicupgrade help
On Thursday, July 16, 2020, 03:30:36 a.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
On 16/07/2020 01:59, Carl Hunter via samba wrote:
>? On Wednesday, July 15, 2020, 05:03:52 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
>?
>?
>? On 15/07/2020 21:53, Carl Hunter via samba wrote:
>>? ? On Wednesday, July 15, 2020,
2016 Oct 25
3
Samba 4.5 y opensuse42.1
Hi friends:
I was installed Samba4 ver 4.5 on openSuSE 42.1 Leap, the smb.conf is:
# Global parameters
[global]
netbios name = SERVERDOM
realm = POLRMVAR.MTZ.SLD.CU
workgroup = POLRMVAR
dns forwarder = 10.44.0.5
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbind, ntp_signd, kcc
[netlogon]
2020 Jul 17
2
Ubuntu 18.04 classicupgrade help
On 17/07/2020 15:05, Carl Hunter via samba wrote:
> On Thursday, July 16, 2020, 07:34:26 a.m. EDT, Carl Hunter via samba <samba at lists.samba.org> wrote:
>
>
> On Thursday, July 16, 2020, 03:30:36 a.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote:
>
>
> On 16/07/2020 01:59, Carl Hunter via samba wrote:
>> ? On Wednesday,
2016 Aug 03
0
Samba 4.2.14 Group Policy (GPO) sync error
> Can you run on a failing computer :
> - netdom verify yourpcname
It seems to work only with FQDN:
C:\Temp>netdom verify cyb64w10-monster
The format of the specified computer name is invalid.
The command failed to complete successfully.
C:\Temp>netdom verify cyb64w10-monster.ad.cyberdyne.local
The secure channel from CYB64W10-MONSTER.AD.CYBERDYNE.LOCAL to the domain
CYBERDYNE