Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem
Did you made a testparm -vv|grep cldap, then press enter You may see this: server services = smb, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate cldap port = 389 First of all server services must point to cldap And the cldap port. If you have another service running on the same port it will not work(ex.: openldap does the same port) Thanks for the tip but I get exactly the same grep output; all server services are pointing to port 389. I've built a couple of fresh systems in order to test this Samba installation so besides SSH nothing is listening yet on any other port besides 22 and no firewall running. Maybe I should use OpenLDAP as an alternative backend for Samba but after some quick googling I've been reading a lot of reports that OpenLDAP no longer supports UDP.. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem
Did you bind to an interface? Interfaces= xxx.xxx.xxx.xxx Is your dns server running and pointing to the samba ads? What about the firewall? --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: jell...@sthuma.nl [mailto:jell...@sthuma.nl] Im Auftrag von Oeboema Gesendet: Freitag, 12. November 2010 09:11 An: muel...@tropenklinik.de Cc: Michael Wood; samba@lists.samba.org; samba-techni...@lists.samba.org Betreff: Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem Did you made a testparm -vv|grep cldap, then press enter You may see this: server services = smb, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate cldap port = 389 First of all server services must point to cldap And the cldap port. If you have another service running on the same port it will not work(ex.: openldap does the same port) Thanks for the tip but I get exactly the same grep output; all server services are pointing to port 389. I've built a couple of fresh systems in order to test this Samba installation so besides SSH nothing is listening yet on any other port besides 22 and no firewall running. Maybe I should use OpenLDAP as an alternative backend for Samba but after some quick googling I've been reading a lot of reports that OpenLDAP no longer supports UDP.. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem
On 12/11/2010 01:06, Oeboema wrote: Samba 4 Alpha 11 is pretty old now. Have you tried Alpha 13? I don't know if it will fix the problem, of course, but I think it's worth a try. Alpha 11 is the latest version available in the FreeBSD ports. Because of the amount of patches and the outstanding work of the port maintainer I would l stick to this one. I will however try to compile alpha 13 myself but this will take a lot of time... We manage in our build farm to build for freebsd 7.2 without any special patches, what are the patches in the freebsd port of samba alpha 11 ? Why not try to make most of them land in main tree ? We can only recommend to move to recent version (or better lastest git snapshot) as alpha11 is 1 year old and given the development pace it's like really old history. Matthieu Patou Samba Teamhttp://samba.org Private repo http://git.samba.org/?p=mat/samba.git;a=summary -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem
On 11 November 2010 22:57, Oeboema oebo...@sthuma.nl wrote: I've been trying to run samba4 alpha11 on a FreeBSD 8.1 system as a Samba 4 Alpha 11 is pretty old now. Have you tried Alpha 13? I don't know if it will fix the problem, of course, but I think it's worth a try. domain controller but I'm having trouble starting the cldapd server. For some reason it won't bind to the specified address or interface whatever I specify in smb.conf. I managed running the provision script without any trouble but I have no clue how to solve this problem in order to start the samba server. Are you specifying a particular interface/address in smb.conf? Do you need to? bitrot# samba4 -i -M single -d3 lp_load: refreshing parameters from /usr/local/etc/smb4.conf params.c:pm_process() - Processing configuration file /usr/local/etc/smb4.conf Processing section [globals] Processing section [netlogon] Processing section [sysvol] adding hidden service IPC$ adding hidden service ADMIN$ samba version 4.0.0alpha11 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 GENSEC backend 'sasl-DIGEST-MD5' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered GENSEC backend 'schannel' registered GENSEC backend 'spnego' registered GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'ntlmssp' registered NTPTR backend 'simple_ldb' NTVFS backend 'simple' for type 1 registered NTVFS backend 'cifs' for type 1 registered NTVFS backend 'nbench' for type 1 registered NTVFS backend 'unixuid' for type 1 registered NTVFS backend 'unixuid' for type 3 registered NTVFS backend 'unixuid' for type 2 registered NTVFS backend 'cifsposix' for type 1 registered NTVFS backend 'smb2' for type 1 registered NTVFS backend 'default' for type 2 registered NTVFS backend 'default' for type 3 registered NTVFS backend 'default' for type 1 registered NTVFS backend 'posix' for type 1 registered PROCESS_MODEL 'standard' registered PROCESS_MODEL 'prefork' registered PROCESS_MODEL 'thread' registered PROCESS_MODEL 'single' registered AUTH backend 'winbind_samba3' registered AUTH backend 'winbind' registered AUTH backend 'winbind_wbclient' registered AUTH backend 'server' registered AUTH backend 'name_to_ntstatus' registered AUTH backend 'fixed_challenge' registered AUTH backend 'unix' registered AUTH backend 'anonymous' registered AUTH backend 'sam' registered AUTH backend 'sam_ignoredomain' registered SHARE backend [ldb] registered. SHARE backend [classic] registered. ldb_wrap open of sam.ldb ldb_wrap open of privilege.ldb ldb_wrap open of /usr/local/etc/samba/private/schannel.ldb samba: using 'single' process model added interface ip=192.168.162.2 nmask=255.255.255.0 DCERPC endpoint server 'wkssvc' registered DCERPC endpoint server 'drsuapi' registered DCERPC endpoint server 'spoolss' registered DCERPC endpoint server 'winreg' registered DCERPC endpoint server 'epmapper' registered DCERPC endpoint server 'srvsvc' registered DCERPC endpoint server 'netlogon' registered DCERPC endpoint server 'browser' registered DCERPC endpoint server 'rpcecho' registered DCERPC endpoint server 'unixinfo' registered DCERPC endpoint server 'samr' registered DCERPC endpoint server 'remote' registered DCERPC endpoint server 'dssetup' registered DCERPC endpoint server 'lsarpc' registered added interface ip=192.168.162.2 nmask=255.255.255.0 added interface ip=192.168.162.2 nmask=255.255.255.0 added interface ip=192.168.162.2 nmask=255.255.255.0 added interface ip=192.168.162.2 nmask=255.255.255.0 added interface ip=192.168.162.2 nmask=255.255.255.0 Failed to bind to ipv4:192.168.162.2:389 - NT_STATUS_INVALID_PARAMETER task_server_terminate: [cldapd failed to setup interfaces] samba_terminate: cldapd failed to setup interfaces -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem
Samba 4 Alpha 11 is pretty old now. Have you tried Alpha 13? I don't know if it will fix the problem, of course, but I think it's worth a try. Alpha 11 is the latest version available in the FreeBSD ports. Because of the amount of patches and the outstanding work of the port maintainer I would l stick to this one. I will however try to compile alpha 13 myself but this will take a lot of time... Are you specifying a particular interface/address in smb.conf? Do you need to? Without any interface/address in smb.conf the same problem occurs. You're correct that I do not have to specify any interface/address but was hoping this would kickstart cldapd. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem
Did you made a testparm -vv|grep cldap, then press enter You may see this: server services = smb, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate cldap port = 389 First of all server services must point to cldap And the cldap port. If you have another service running on the same port it will not work(ex.: openldap does the same port) Greetings Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Oeboema Gesendet: Donnerstag, 11. November 2010 23:07 An: Michael Wood Cc: samba@lists.samba.org; samba-techni...@lists.samba.org Betreff: Re: [Samba] FreeBSD 8.1 Samba4 alpha11 domain controller - cldapd bind problem Samba 4 Alpha 11 is pretty old now. Have you tried Alpha 13? I don't know if it will fix the problem, of course, but I think it's worth a try. Alpha 11 is the latest version available in the FreeBSD ports. Because of the amount of patches and the outstanding work of the port maintainer I would l stick to this one. I will however try to compile alpha 13 myself but this will take a lot of time... Are you specifying a particular interface/address in smb.conf? Do you need to? Without any interface/address in smb.conf the same problem occurs. You're correct that I do not have to specify any interface/address but was hoping this would kickstart cldapd. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
