On Sun, 2013-05-19 at 16:27 +0800, wong lmark wrote: > Please let me simplify the question. I chose the in place upgrade > Samba 3 to Samba 4 in my CentOS 6.4.
Hi Ok, so this Domain has been produced by: /usr/local/samba/bin/samba-tool domain classicupgrade /etc/samba/smb.conf --dbdir=/var/lib/samba/ --use-xattrs=yes --realm=TEST.COM And this is the log for the first run when you typed samba: > Firstly, I used "/usr/local/samba/bin/smbclient -L localhost -U%" and > got a message "Connection to localhost failed (Error > NT_STATUS_CONNECTION_REFUSED)". > I read the log.samba and got the error : > > [2013/05/19 15:27:41, > 0] ../source4/smbd/server.c:369(binary_smbd_main) > samba version 4.0.5 started. > Copyright Andrew Tridgell and the Samba Team 1992-2012 > [2013/05/19 15:27:41, > 0] ../source4/smbd/server.c:475(binary_smbd_main) > samba: using 'standard' process model > [2013/05/19 15:27:41, > 0] ../source4/lib/tls/tlscert.c:70(tls_cert_generate) > Attempting to autogenerate TLS self-signed keys for https for > hostname 'SAM.test.com' > [2013/05/19 15:27:41, > 0] ../source4/lib/tls/tlscert.c:166(tls_cert_generate) > TLS self-signed keys generated OK > [2013/05/19 15:27:43, > 0] ../source4/smbd/service_stream.c:342(stream_setup_socket) > Failed to listen on 0.0.0.0:389 - > NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > [2013/05/19 15:27:43, > 0] ../source4/ldap_server/ldap_server.c:821(add_socket) > ldapsrv failed to bind to 0.0.0.0:389 - > NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > [2013/05/19 15:27:43, > 0] ../source4/smbd/service_task.c:35(task_server_terminate) > task_server_terminate: [Failed to startup ldap server task] > [2013/05/19 15:27:43, > 0] ../source4/smbd/server.c:210(samba_terminate) > samba_terminate: Failed to startup ldap server task > [2013/05/19 15:39:06, > 0] ../file_server/file_server.c:47(file_server_smbd_done) > file_server smbd daemon exited normally > [2013/05/19 15:39:06, > 0] ../source4/smbd/service_task.c:35(task_server_terminate) > task_server_terminate: [smbd child process exited] > > > Second, I used "kinit Administrator" or "kinit root", the message is > shown "kinit: Cannot resolve servers for KDC in realm "Test.com" while > getting initial credentials" > > > How can I solve that? I'd go for DNS. A good start is /etc/hosts. Is there an entry for sam.test.com? What does /etc/krb5.conf contain? Cheers, Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
