On 07/18/2019 10:41 AM, Rowland penny via samba wrote:> > Anything from here on is nothing to do with your problem, it? is just > artefacts of the clean up. > > It seems to be failing whilst trying to add the 'A' record for your > new DC. > > Lets backtrack a little, I asked if the Windows DC was running a dns > server and you answered 'yes'. Lets expand that a little, what dns > server is running and where does it store the dns records ?The one that comes with windows.? You manage it from the dnsmgmt console. -- Bob Wooldridge EDM Incorporated
On 18/07/2019 16:44, Robert A Wooldridge via samba wrote:> > On 07/18/2019 10:41 AM, Rowland penny via samba wrote: >> >> Anything from here on is nothing to do with your problem, it? is just >> artefacts of the clean up. >> >> It seems to be failing whilst trying to add the 'A' record for your >> new DC. >> >> Lets backtrack a little, I asked if the Windows DC was running a dns >> server and you answered 'yes'. Lets expand that a little, what dns >> server is running and where does it store the dns records ? > The one that comes with windows.? You manage it from the dnsmgmt console. >I have never had to deal with a W2K AD server, but from my understanding W2K didn't have the DNS records in AD, so I wondered if yours didn't either. I am running out of ideas now. Have you tried Tim's patch ? Just in case you don't know how to apply the patch, it is pretty simple, it just involves commenting out three lines, so it might be easier to open 'join.py (/usr/lib/python2.7/dist-packages/samba/join.py on my DC), find these lines: ??????????? if ctx.dns_backend != "NONE": ??????????????? ctx.join_add_dns_records() ??????????????? ctx.join_replicate_new_dns_records() Line 1405 in my version, under '??? def do_join(ctx):' just comment out those three lines, save & close, then try the join again. Rowland
On 07/18/2019 11:04 AM, Rowland penny via samba wrote:> On 18/07/2019 16:44, Robert A Wooldridge via samba wrote: >> >> On 07/18/2019 10:41 AM, Rowland penny via samba wrote: >>> >>> Anything from here on is nothing to do with your problem, it is just >>> artefacts of the clean up. >>> >>> It seems to be failing whilst trying to add the 'A' record for your >>> new DC. >>> >>> Lets backtrack a little, I asked if the Windows DC was running a dns >>> server and you answered 'yes'. Lets expand that a little, what dns >>> server is running and where does it store the dns records ? >> The one that comes with windows.? You manage it from the dnsmgmt >> console. >> > I have never had to deal with a W2K AD server, but from my > understanding W2K didn't have the DNS records in AD, so I wondered if > yours didn't either. I am running out of ideas now.This is not a W2K machine but Server 2003.> > Have you tried Tim's patch ?No, will give it a try.> > Just in case you don't know how to apply the patch, it is pretty > simple, it just involves commenting out three lines, so it might be > easier to open 'join.py > (/usr/lib/python2.7/dist-packages/samba/join.py on my DC), find these > lines: > > ??????????? if ctx.dns_backend != "NONE": > ??????????????? ctx.join_add_dns_records() > ??????????????? ctx.join_replicate_new_dns_records() > > Line 1405 in my version, under '??? def do_join(ctx):' > > just comment out those three lines, save & close, then try the join > again. > > Rowland > > >-- Bob Wooldridge EDM Incorporated
On 07/18/2019 11:04 AM, Rowland penny via samba wrote:> I have never had to deal with a W2K AD server, but from my > understanding W2K didn't have the DNS records in AD, so I wondered if > yours didn't either. I am running out of ideas now. > > Have you tried Tim's patch ? > > Just in case you don't know how to apply the patch, it is pretty > simple, it just involves commenting out three lines, so it might be > easier to open 'join.py > (/usr/lib/python2.7/dist-packages/samba/join.py on my DC), find these > lines: > > ??????????? if ctx.dns_backend != "NONE": > ??????????????? ctx.join_add_dns_records() > ??????????????? ctx.join_replicate_new_dns_records()This seems to have worked.? I got a successful join. But samba is not running.? When I do systemctl status samba I get: Unit samba.service could not be found. When I do systemctl status smbd I get: ? smbd.service - Samba SMB Daemon ?? Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled) ?? Active: failed (Result: exit-code) since Thu 2019-07-18 11:21:22 CDT; 6min ago ???? Docs: man:smbd(8) ?????????? man:samba(7) ?????????? man:smb.conf(5) ? Process: 992 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) ? Process: 1002 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE) ?Main PID: 1002 (code=exited, status=1/FAILURE) Jul 18 11:21:22 athena systemd[1]: Starting Samba SMB Daemon... Jul 18 11:21:22 athena smbd[1002]: [2019/07/18 11:21:22.721995,? 0] ../source3/smbd/server.c:1803(main) Jul 18 11:21:22 athena smbd[1002]:?? server role = 'active directory domain controller' not compatible with running smbd standalone. Jul 18 11:21:22 athena smbd[1002]:?? You should start 'samba' instead, and it will control starting smbd if required Jul 18 11:21:22 athena systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE Jul 18 11:21:22 athena systemd[1]: smbd.service: Failed with result 'exit-code'. Jul 18 11:21:22 athena systemd[1]: Failed to start Samba SMB Daemon. -- Bob Wooldridge EDM Incorporated