search for: eisofen

Hi, last weekend I've updated samba and ctdb on my 2-node cluster. Samba is now on 3.5.6 (from 3.3.4), ctdb on 1.0.114 (from 1.0.84). Both installed from repo via yum and ctdb-packages. After restarting both nodes everything was fine, we could access files on the cluster. On monday I noticed that the nodes didn't had their initial adresses: Node 1: hostname dscln01, public IP

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, currently I'm testing samba authenticating against ADS. Samba is joined to that domain, getent passwd and wbinfo -u works as expected, but when I try to ssh to the samba server with an account in AD it failes. I've turned debug on for pam_winbind.so in /etc/pam.d/system-auth. When I try to connect I get the following in /var/log/secure

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm in the progress of setting up clustered samba with ctdb. Samba is ADS-member server. WINS server is configured on two of our 2003-servers. When samba runs for a couple of hours I checked the WINS servers and saw that samba/nmbd registrred only the private interface addresses (192.168.1.x) and not the public interfaces (10.0.0.41,42).

Hi, (this will be a long post) currently we got a working setup of one PDC in our HQ and five BDC in our branch offices, all backed by LDAP. PDC is LDAP master and all branch offices are configured as syncrepl. This setup was more a playfield for me, which 'suddenly' went into production by business needs, you know the deal... The setup does a fine job, but there is no failover of any