Displaying 12 results from an estimated 12 matches for "stream_setup_socket".
2019 Jun 11
2
NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot
...)
Failed to bind to ipv4:152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.782813, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
task_server_terminate: [cldapd failed to setup interfaces]
[2019/06/11 09:23:47.788484, 0] ../source4/smbd/service_stream.c:360(stream_setup_socket)
Failed to listen on 152.94.0.106:88 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.788606, 0] ../source4/kdc/kdc-server.c:584(kdc_add_socket)
Failed to bind to 152.94.0.106:88 TCP - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.788675, 0] ../source4/smbd/service_task.c:35(ta...
2019 Jul 23
4
Problems after upgrade Samba 4
...2586, 0] ../../source4/smbd/server.c:773(binary_smbd_main)
Jul 23 10:19:25 samba4-dc samba: root process[823]: binary_smbd_main:
samba: using 'standard' process model
Jul 23 10:19:26 samba4-dc samba: task[dns][838]: [2019/07/23
10:19:26.025682, 0]
../../source4/smbd/service_stream.c:374(stream_setup_socket)
Jul 23 10:19:26 samba4-dc samba: task[dns][838]: stream_setup_socket:
Failed to listen on :::53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Jul 23 10:19:26 samba4-dc samba: task[dns][838]: [2019/07/23
10:19:26.025819, 0]
../../source4/dns_server/dns_server.c:649(dns_add_socket)
Jul 23 10:19:26 samba...
2019 Jun 11
0
NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot
...nd to ipv4:152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.782813, 0] ../source4/smbd/service_task.c:35(task_server_terminate)
> task_server_terminate: [cldapd failed to setup interfaces]
> [2019/06/11 09:23:47.788484, 0] ../source4/smbd/service_stream.c:360(stream_setup_socket)
> Failed to listen on 152.94.0.106:88 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.788606, 0] ../source4/kdc/kdc-server.c:584(kdc_add_socket)
> Failed to bind to 152.94.0.106:88 TCP - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.788675, 0] ../source4/smb...
2019 Jun 11
1
NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot
...> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.782813, 0]
> ../source4/smbd/service_task.c:35(task_server_terminate)
> > task_server_terminate: [cldapd failed to setup interfaces]
> > [2019/06/11 09:23:47.788484, 0]
> ../source4/smbd/service_stream.c:360(stream_setup_socket)
> > Failed to listen on 152.94.0.106:88 -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.788606, 0] ../source4/kdc/kdc-
> server.c:584(kdc_add_socket)
> > Failed to bind to 152.94.0.106:88 TCP -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11...
2020 Nov 04
2
Active - Deactivating
.../11/03 18:54:19.293928, 0]
../../source4/smbd/server.c:378(samba_terminate)
Nov 03 18:54:19 AD samba[21886]: samba_terminate: samba_terminate of samba
21886: kdc failed to setup interfaces
Nov 03 18:54:19 AD samba[21925]: [2020/11/03 18:54:19.319591, 0]
../../source4/smbd/service_stream.c:374(stream_setup_socket)
Nov 03 18:54:19 AD samba[21925]: stream_setup_socket: Failed to listen on
0.0.0.0:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Nov 03 18:54:19 AD samba[21925]: [2020/11/03 18:54:19.319686, 0]
../../source4/dns_server/dns_server.c:649(dns_add_socket)
Nov 03 18:54:19 AD samba[21925]: Failed to...
2020 Nov 20
2
Confusing errors when attempting to run samba in AD DC mode
...11/19 05:09:52.224499, 0] ../../source4/dsdb/dns/dns_update.c:85(dnsupdate_nameupdate_done)
Nov 19 05:09:52 pluto samba[1096]: dnsupdate_nameupdate_done: Failed DNS update with exit code 1
Nov 19 05:10:00 pluto samba[1066]: [2020/11/19 05:10:00.273975, 0] ../../source4/smbd/service_stream.c:372(stream_setup_socket)
Nov 19 05:10:00 pluto samba[1066]: stream_setup_socket: Failed to listen on :::389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Nov 19 05:10:00 pluto samba[1066]: [2020/11/19 05:10:00.273975, 0] ../../source4/ldap_server/ldap_server.c:1185(add_socket)
Nov 19 05:10:00 pluto samba[1066]: add_socket:...
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
...Process: 17808 ExecStart=/usr/sbin/samba --foreground --no-process-group $SAMBAOPTIONS (code=exited, status=1/FAILURE)
Main PID: 17808 (code=exited, status=1/FAILURE)
Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: [2020/02/27 16:35:18.492522, 0] ../source4/smbd/service_stream.c:371(stream_setup_socket)
Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: stream_setup_socket: Failed to listen on 0.0.0.0:389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: [2020/02/27 16:35:18.492563, 0] ../source4/ldap_server/ldap_server.c:1036(add_socket)...
2020 Feb 28
0
Samba AD - Different IP than the existing one assigned
...ground
> --no-process-group $SAMBAOPTIONS (code=exited, status=1/FAILURE)
>
> Main PID: 17808 (code=exited, status=1/FAILURE)
>
>
>
> Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]:
> [2020/02/27 16:35:18.492522, 0]
> ../source4/smbd/service_stream.c:371(stream_setup_socket)
>
> Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]:
> stream_setup_socket: Failed to listen on 0.0.0.0:389 -
> NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
>
> Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]:
> [2020/02/27 16:35:18.492563, 0]
> ../source4/...
2015 Mar 23
1
Samba4 classic upgrade problem
...(tls_cert_generate)
Attempting to autogenerate TLS self-signed keys for https for hostname
'SOMEDOM.somedom.local'
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
[2015/03/17 14:49:46.848705, 0]
../source4/smbd/service_stream.c:346(stream_setup_socket)
Failed to listen on 0.0.0.0:464 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2015/03/17 14:49:46.848876, 0] ../source4/kdc/kdc.c:672(kdc_add_socket)
Failed to bind to 0.0.0.0:464 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2015/03/17 14:49:46.848976, 0]
../source4/smbd/service_task.c:35(task_serv...
2020 Oct 18
3
Samba does not work after upgrade to Ubuntu 20.04.1
...1-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
[2020/10/16 01:31:48.239372, 0] ../../source4/smbd/server.c:865(binary_smbd_main)
binary_smbd_main: samba: using 'prefork' process model
[2020/10/16 01:31:51.047803, 0] ../../source4/smbd/service_stream.c:374(stream_setup_socket)
stream_setup_socket: Failed to listen on 0.0.0.0:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2020/10/16 01:31:51.158918, 0] ../../source4/dns_server/dns_server.c:649(dns_add_socket)
Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2020/10/16 01:31:51.447228, 0] ../...
2013 May 18
3
security=ads
Dear samba-mailinglist,
We're using samba 4.0.5 as an active directory domain controller.
We used to set up some file shares on basis security=user in the old
samba version. I was able to set up the shares as they used to be .
My Question:
How can I set up "wich user kan read/write which share?"
Do I have to do this in den Active Directory or in smb.conf?
This maybe a trivial
2014 Mar 18
2
DNS error on startup Samba4 ADS mode DC
...urce4/lib/tls/tlscert.c:70(tls_cert_generate)
Mar 17 17:39:07 mythtv-0 samba[9956]: Attempting to autogenerate TLS self-signed keys for https for hostname 'MYTHTV-0.dmz.meanspc.com'
Mar 17 17:39:07 mythtv-0 samba[9964]: [2014/03/17 17:39:07.758518, 0] ../source4/smbd/service_stream.c:346(stream_setup_socket)
Mar 17 17:39:07 mythtv-0 samba[9964]: Failed to listen on 192.168.101.170:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Mar 17 17:39:07 mythtv-0 samba[9964]: [2014/03/17 17:39:07.781551, 0] ../source4/dns_server/dns_server.c:623(dns_add_socket)
Mar 17 17:39:07 mythtv-0 samba[9964]: Failed to bind...