Is it possible to have samba4 DC with samba 3.4.7 file server?
d.dario76 at gmail.com
Tue Jun 26 04:18:19 MDT 2012
trying to fix the issues in my previous mail, I found that disabling
s3fs on both DCs, the samba 3.4.7 servers restarted working.
To get this I added these lines:
server services = +smb -s3fs
dcerpc endpoint servers = +winreg +srvsvc
Is it possible that the problem was that I missed to enable some
services on smb.conf to use s3fs? I let it as default 'cause I've heard
that s3fs was the default.
In my network, the PDC runs on a VM and due to low space on it's disk it
will stay AD DC and DNS server (up to now with bind+DLZ) but BDC is a
physical server and runs AD DC and DNS server but it should also became
the file server so I need to get s3fs working.
On Tue, 2012-06-26 at 09:23 +0200, Daniele Dario wrote:
> Hi list,
> today I updated my two samba4 DCs to latest git tree (Version
> Before to update secodary DC I demoted it to test DNS zones replication
> after a re-join and I was very happy to see that after join, zones
> automatically started to replicate (and now I have full replica of them)
> and with samba_upgradedns I was able to get private/dns stuff and than
> bind9 with DLZ backend worked fine (haven't yet tested to add entries on
> secondary DC but will try soon).
> I had a problem with the creation of the CNAME record of the re-joined
> DC in the _msdcs zone (I had remove the old one and add the new one with
> samba-tool) but after that, all went fine.
> After that I rebooted the two file servers with samba 3.4.7 but they
> came up with this problem:
> [2012/06/25 17:03:17, 1, pid=1140]
> Could not receive trustdoms
> [2012/06/25 17:03:17, 1, pid=1140] libads/ldap.c:427(ads_find_dc)
> ads_find_dc: failed to find a valid DC on our site
> (Default-First-Site-Name), trying to find another DC
> Now, domain users can't map network shares.
> Also smbclient (both from file servers samba 3.4.7 and from DCs samba4)
> is not able to list shares:
> [root at kdc02:/usr/local/samba]# smbclient -L localhost -U%
> Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)
> Anyone has had these issues or can tell me how fix the problem?
> I'll test s3fs on samba4 before to migrate from 3.4.7 our network shares
> but one of the 3.4.7 servers is used to allow logins from the internet
> to our LAN so for now I need to keep it a 3.
> Thanks in advance for your kind help,
More information about the samba-technical