pgarciaSorry I have only come across this now, but have you seen:
http://trac.zentyal.org/wiki/Document/HowTo/EBoxMasterSlaveSetupparticularly the section referred to as Slave. I can see why
eboxbuggy used that term in the title of this topic now. I don't know if it is fully relevant to version 2.0 of Zentyal but looking at my firewall I see that LDAP connections are not allowed thru by default. It would need to be enabled, at least for internal networks. The other thing to remember is to have the slave LDAP synchronised to the master after the master is set up - should be checkable using an output (from
slapcat) of the LDAP db from each server and comparing them. Another thing to remember is that the use of
ldaps protocol that I suggested may complicate things so perhaps
ldap should be used as the connection protocol (although not secure) because as you can see from my everything in one server, it is used internally:
adminuser@tim-z1:~$ netstat -ta |grep ldap
tcp 0 0 *:ldap *:* LISTEN
tcp 0 0 *:ldaps *:* LISTEN
tcp 0 0 localhost:ldap localhost:35582 ESTABLISHED
tcp 0 0 localhost:35582 localhost:ldap ESTABLISHED
tcp 0 0 localhost:ldap localhost:36043 ESTABLISHED
tcp 0 0 localhost:36043 localhost:ldap ESTABLISHED
tcp6 0 0 [::]:ldap [::]:* LISTEN
tcp6 0 0 [::]:ldaps [::]:* LISTEN
adminuser@tim-z1:~$
See if you can see the connections between your master and slave LDAP servers using a command similar to the above to prove that the links are there.
It might be helpful if you provide more log information. Look for relevant lines at the tail of the
messages log and/or
syslog. Also what sort of error is reported in the PC logs at
C:\Windows\Debug where the relevant file should be
netlogon. See the sort of error output that
eboxbuggy provides.
As to the other endpoint errors appearing - here are my logs around the time of my first successful join of a domain on 2010/11/26:
[2010/11/18 23:21:18, 0] lib/util_sock.c:738(write_data)
[2010/11/18 23:21:18, 0] lib/util_sock.c:1491(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2010/11/18 23:21:18, 0] smbd/process.c:62(srv_send_smb)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
[2010/11/26 19:51:46, 0] lib/util_sock.c:738(write_data)
[2010/11/26 19:51:46, 0] lib/util_sock.c:1491(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2010/11/26 19:51:46, 0] smbd/process.c:62(srv_send_smb)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
[2010/11/26 19:51:48, 1] smbd/service.c:1063(make_connection_snum)
laurence-f1 (192.168.192.224) connect to service profiles initially as user bamalam (uid=0, gid=1901) (pid 4083)
[2010/11/26 19:51:48, 1] smbd/service.c:1063(make_connection_snum)
laurence-f1 (192.168.192.224) connect to service netlogon initially as user bamalam (uid=2002, gid=1901) (pid 4083)
[2010/11/26 19:51:53, 1] smbd/service.c:1063(make_connection_snum)
laurence-f1 (192.168.192.224) connect to service bamalam initially as user bamalam (uid=2002, gid=1901) (pid 4083)
[2010/11/26 19:51:59, 1] smbd/service.c:1240(close_cnum)
laurence-f1 (192.168.192.224) closed connection to service profiles
[2010/11/26 19:51:59, 1] smbd/service.c:1240(close_cnum)
laurence-f1 (192.168.192.224) closed connection to service netlogon
[2010/11/26 19:51:59, 1] smbd/service.c:1240(close_cnum)
laurence-f1 (192.168.192.224) closed connection to service bamalam
[2010/11/26 19:52:06, 1] smbd/service.c:1063(make_connection_snum)
laurence-f1 (192.168.192.224) connect to service bamalam initially as user bamalam (uid=2002, gid=1901) (pid 4083)
[2010/11/26 19:52:06, 1] smbd/service.c:1063(make_connection_snum)
laurence-f1 (192.168.192.224) connect to service netlogon initially as user bamalam (uid=2002, gid=1901) (pid 4083)
[2010/11/26 19:54:47, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
You can see that some of the same endpoint errors don't seem to have made a difference to a successful outcome.
Finally as brought to my attention by the problems of
eboxbuggy, the
sambaProfilePath and
sambaHomePath should be correct and the samba server reachable from the LDAP servers.