search for: 636

Hello All, We have interesting issue. When application connect to PDC by port 389 (without ssl) everything works fine. When we try to use SSL by port 636 we have issue. ldapsearch -x -D "cn=user,ou=users,dc=dc,dc=local" -p 636 -h PDC -b "DC=dc,DC=local" -w pass output: ldap_result: Can't contact LDAP server (-1) ldapsearch -x -D "cn=user,ou=users,dc=dc,dc=local" -p 636 -h PDC -b "DC=dc,DC=local" -w p...

...ldap_connect_system: Binding to ldap server as "cn=manager,dc=corman,dc=be" [2003/03/26 14:28:04, 0] passdb/pdb_ldap.c:ldap_connect_system(316) ldap_connect_system: Binding to ldap server as "cn=manager,dc=corman,dc=be" [2003/03/26 14:29:41, 1] smbd/service.c:make_connection(636) donglesvr (10.217.7.11) connect to service print$ as user root (uid=0, gid=0) (pid 16328) [2003/03/26 14:29:49, 1] smbd/service.c:make_connection(636) donglesvr (10.217.7.11) connect to service print$ as user root (uid=0, gid=0) (pid 16328) [2003/03/26 14:29:49, 1] smbd/service.c:close_cnum(67...

Hello Vinicius, I did it and this was the answer: ldapsearch -H "ldaps://devsamba.lucas.ufes.br:636" -w '*********' -D "cn=administrator,cn=users,dc=lucas,dc=ufes,dc=br" -x -b "dc=lucas,dc=ufes,dc=br" -d1 ldap_url_parse_ext(ldaps://devsamba.lucas.ufes.br:636) ldap_create ldap_url_parse_ext(ldaps://devsamba.lucas.ufes.br:636/??base) ldap_sasl_bind ldap_send_initial...

..., sorry if I disturb you. I configured samba+ldap as a PDC and byt now it's working fine, so, I decided to put some security to the stuff. The problem is that I coudl not make it work, here I what I've done. This is what netstat shows. tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:636 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:389 127.0.0.1:1873 ESTABLISHED tcp 0 0 :::389 :::* LISTEN tcp 0 0 :::636 :::* LISTEN in slapd.conf i have TLSCipherSuite HIGH:MEDIUM:+SSLv3 TLSCertificateFile /usr/local/etc/openldap/ssl/server.crt TLSCertificateKeyFile /usr/local/etc/openldap/ssl/server.key Ve...

...p on a machine (the names are changed to protect the innocent) example.mydomain.com running CentOS 5.4 and LDAP version 2.3.43-3. If I issue a ldapsearch command while logged onto the LDAP server host I get a valid response back. For example: > ldapsearch -x -LLL -H ldaps://example.mydomain.com:636 "(uid=joker)" \ > sn uid dn: uid=joker,ou=People,dc=mydomain,dc=com uid: joker sn: Nicholson Everything works as expected. However if I try the same command from a remote machine remote.mydomain.com the command just hangs. I can not find a log entry anywhere that indicates something i...

...ads` and `idmap config OURDOMAIN : backend = ad`, resp., among others). So, if I understand this correctly authentication is done via Kerberos and authorization via LDAP. Unfortunately (but understandably), our central IT department recently disable standard LDAP (port 389) in favour of LDAPS (port 636). Since then, I can only authentica user (e.g. `wbinfo -u` and `wbinfo -a someuser` work). But not further authorize them (e.g. `wbinfo -g`, `wbinfo --user-info someuser`, `wbinfo -S somesid` or `id someuser` fail or give no output). Consequently, users can not mount their samba shares anymore. And...

http://bugzilla.mindrot.org/show_bug.cgi?id=636 Summary: configure.ac patch for unicosmp machine Product: Portable OpenSSH Version: -current Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Build system Assig...

...y the first ldap server is used and if unavailable none of the other backends are going to be tried. Samba then still tries to connect over and over to the unavailable eDirectory-Server. My passdb entry looks like this (it?s all in one line): passdb backend = NDS_ldapsam:ldaps://serverA.blabla.com:636 NDS_ldapsam:ldaps://serverB.blabla.com:636 NDS_ldapsam:ldaps://serverC.blabla.com:636 smbpasswd If i use the notation for ldapsam in the way it?s mentioned in the documentation it does not work at all: passdb backend = NDS_ldapsam:"ldaps://serverA.blabla.com:636 ldaps://serverB.blabla.com:636...

Hello Brian, Sorry to my late answer, I did what you suggest previously This error suggests a problem with your certificate. If it used to work previously, then check it hasn't expired. openssl s_client -connect devsamba.lucas.ufes.br:636 copy-paste the certificate into a pem file, including begin/end lines openssl x509 -in mycert.pem -noout -enddate And check your root CA cert hasn't expired: openssl x509 -in /usr/local/samba/private/tls/cert.pem -noout -enddate I did the first command and I got this: openss...

...4/03/17 21:57:36.011497, 0] ../lib/util/fault.c:144(smb_panic_default) PANIC: internal error Same error we get on command line with this command: samba-tool dns query ad01.domain.test domain.test @ ALL -UAdministrator netstat before connecting : netstat -anp | grep '88\|135\|389\|464\|636\|1024\|3268\|3269\|53' | grep -i listen tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN 27695/samba tcp 0 0 10.30.0.2:53 0.0.0.0:* LISTEN 26519/named-sdb tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 26519/named-sdb tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 27695/samba tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 26519/...

I'm trying to confirm that LDAP traffic is encrypted on my Samba 4 DC. I have read and followed https://wiki.samba.org/index.php/Setup_LDAPS_on_a_DC but when I attempt to connect to the DC on port 636 or via ldaps:// or both via ldapsearch (linux) and ldp (windows) I cannot connect. Failed tests: *ldapsearch -I -H ldaps://dc* ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1) additional info: (unknown error code) *ldapsearch -I -H ldaps://dc:636* ldap_sasl_interactive_bi...

Hello Samba Team, We have AD controller with opened ldap ports (389/636). Problem is that users can connect by application like Apache DIrectory Studio and they see all ldap tree. Is it any solution to: - block view for all users without specific ACL, - block same attribute like uidNumber ? I'm lokking something like ACL in OpenLdap for Samba AD. Maybe somebody...

http://bugzilla.netfilter.org/show_bug.cgi?id=636 Summary: iptables exits with segmentation fault when protocol name is wrong Product: iptables Version: unspecified Platform: x86_64 OS/Version: Gentoo Status: NEW Severity: normal Priority: P1...

I have a Samba file server attempting to join an Active Directory domain using "$net ads join". The Domain Controller is running Windows Server 2019. I'd like to force samba to use port 636 (LDAPS) when making the LDAP connection. I've tried several settings in the smb.conf file, but when I check the LDAP packets, samba is still using port 389. The join domain call is successful, it's just using the wrong port. I've tried: - "ldap ssl ads = yes" -...

Hi, I''ve been trying to boot stefano''s minimal dom0 kernel from git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git 2.6.36-rc1-initial-domain-v2+pat On xen-unstable, I get the following WARN_ON()''s from Xen when bringing up the NIC''s, then the machine hangs forever when trying to login either over serial or NIC. (XEN) Xen WARN at msi.c:649 (XEN) ----[

Am 15.04.24 um 21:14 schrieb Ralph Boehme: > On 4/15/24 10:02, Kuhring, Mathias via samba wrote: >> Is this still the case? > thankfully implementing channel bindings has recently been funded by one of our customers, so LDAPis soon coming (back) to Samba. > > https://gitlab.com/samba-team/samba/-/merge_requests/3516 > > Iirc it will also be available to idmap_ad, but

Anybody know of good reliable Asterisk compatible DIDs in the 636 (Missouri, USA) area code? Voicepulse doesn't go there, and Broadvoice seems unreliable in my Asterisk installation -- so I'm reluctant to recommend it. Thanks, </edg>

Hi Vitaly, 2009/2/26 Vitaly Polyakov <var at fapu.ru> > Hello. > > You are the site administrator Project Network UPS Tools, are not you? I > think? it is a good idea to add information about the compatibility the > NUT with a Mustek PowerMust 424/636/848 USB. These UPS are using > modified protocol, and therefore the old driver megatec_usb is not > suitable and the new driver blazer was created. Details about this, I > hardly found here: > > http://lists.alioth.debian.org/pipermail/nut-upsdev/2008-December/003555.html > > I...

...in] #. / samba-i-M single-d 1 Samba version 4.1.0pre1-GIT-05a5974 started. Copyright Andrew Tridgell and the Samba Team 1992-2012 samba: using 'single' process model Started with smbd server config file / usr/local/samba4-migracao/private/smbd.tmp/fileserver.conf Failed to listen on 0.0.0.0:636 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED ldapsrv failed to bind to 0.0.0.0:636 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED task_server_terminate: [Failed to startup ldap server task] / usr/local/samba4-migracao/sbin/smbd: smbd version 4.1.0pre1-GIT-05a5974 started. / usr/local/samba4-migracao/sbin/smbd: C...

......it's a nightmare over here.... this seems to affect all versions of windows regardless of SP's. log snippet: [2002/10/29 09:58:33, 1] smbd/service.c:close_cnum(677) ct10164 (151.103.27.118) closed connection to service dh354638 [2002/10/29 09:58:33, 1] smbd/service.c:make_connection(636) ct10164 (151.103.27.118) connect to service netlogon as user dh354638 (uid=129 81, gid=206) (pid 410710) [2002/10/29 09:58:33, 1] smbd/service.c:make_connection(636) mr00265 (151.103.23.7) connect to service yr317441 as user yr317441 (uid=21730 , gid=206) (pid 254944) [2002/10/29 09:58:33, 1]...