similar to: Moving from a PDC to an DA

Displaying 20 results from an estimated 9000 matches similar to: "Moving from a PDC to an DA"

2020 Nov 15
0
Moving from a PDC to an DA
On 15/11/2020 03:38, Robert Moskowitz via samba wrote: > This is not an upgrade in place and I am not finding any good > guidance, so here I am asking on the list... > > I have an old PDC that has been running since '12.? The domain is > called Homebase, and the server is called Homebase.? The Samba > software I am using is the ClearOS5 distro. > > Now I have
2015 Sep 07
2
Maybe working - Re: BIND DLZ zone transfers
Hi Robert, yes it does work. But the DLZ bind will not notify any slaves, when the repository changes. This can be painful, especially for longer TTL values. Regards, - lars. Am 07.09.2015 um 20:16 schrieb Robert Moskowitz: > > > On 09/07/2015 12:52 PM, Robert Moskowitz wrote: >> I am looking at: https://wiki.samba.org/index.php/DNS_administration >> >> I am using
2017 May 25
2
Centos7 Cant start vncserver
OK, first time configuring vncserver on Centos7. I have read through a bunch of old messages here on vncserver and thought I had it. Obviously not. 1) cp /usr/lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service 2) vi /etc/systemd/system/vncserver at .service I changed <USER> in both places to root 3) systemctl daemon-reload 4) systemctl
2015 Sep 07
2
Maybe working - Re: BIND DLZ zone transfers
On 07/09/15 21:26, Robert Moskowitz wrote: > Is there some option on the slave to set the frequency of the AXFR? > Say every hour? > > On 09/07/2015 03:45 PM, Lars Hanke wrote: >> Hi Robert, >> >> yes it does work. But the DLZ bind will not notify any slaves, when >> the repository changes. This can be painful, especially for longer >> TTL values.
2015 Sep 03
2
samba_dlz: Failed to connect
On 09/03/2015 01:48 PM, Rowland Penny wrote: > On 03/09/15 18:38, Robert Moskowitz wrote: >> Progress on dns_dlz. At least I got things loading. If I don't >> include the dlz info bind starts, but if I do I get: >> >> Sep 03 13:31:57 homebase.home.htt named[21920]: Loading 'AD DNS Zone' >> using driver dlopen >> Sep 03 13:31:58
2015 Sep 03
1
samba_dlz: Failed to connect
On 09/03/2015 02:12 PM, Rowland Penny wrote: > On 03/09/15 19:01, Robert Moskowitz wrote: >> >> >> On 09/03/2015 01:48 PM, Rowland Penny wrote: >>> On 03/09/15 18:38, Robert Moskowitz wrote: >>>> Progress on dns_dlz. At least I got things loading. If I don't >>>> include the dlz info bind starts, but if I do I get: >>>>
2015 Sep 03
3
samba_dlz: Failed to connect
Progress on dns_dlz. At least I got things loading. If I don't include the dlz info bind starts, but if I do I get: Sep 03 13:31:57 homebase.home.htt named[21920]: Loading 'AD DNS Zone' using driver dlopen Sep 03 13:31:58 homebase.home.htt named[21920]: samba_dlz: Failed to connect to /var/lib/samba/private/dns/sam.ldb permissions seem right: # ls -ls
2015 Sep 10
3
rsync question
On 09/10/15, C Linus Hicks wrote: On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------ Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ --------------------- End Quote ---------------------------------- Sorry, I was too fast, not paying attention, you want this I believe: rsync -ah --stats root at
2015 Aug 28
3
More on bind_dlz - documentation I have not found
Are you setting up a AD DC or old style NT PDC ? see : /etc/default/sernet-samba to "classic". for NT PDC /etc/default/sernet-samba to "ad". for AD DC. greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens >Robert Moskowitz >Verzonden: vrijdag 28 augustus 2015 16:13 >Aan: Rowland Penny; samba at
2015 Sep 11
2
rsync question
On Thu, 10 Sep 2015 22:50:47 -0400 Robert Moskowitz wrote: > > That will use the default port on the remote host, you can override > > that without specifying the -e if required using -p <port>. > > > $ rsync -ah --stats --delete -p 613 root at 192.168.129.2:/etc/dhcp/ > /home/rgm/data/htt/httnet/homebase/new/dhcp > Unexpected remote arg: root at
2018 Aug 03
4
rsync versioning problem
On 08/03/2018 11:07 AM, Warren Young wrote: > On Aug 3, 2018, at 8:57 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: >> I seem to have an rsync versioning problem. > Have you ruled out the other causes of that error? For instance: > > https://askubuntu.com/a/716911 yeah.? It is backups, not backup.? Oops. > >> And researching this it comes down to a
2015 Sep 10
1
rsync question
On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------ I just tried the following: rsync -ah --stats "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ And it failed with: Unexpected remote arg: 192.168.192.2:/root/samba.PDC/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1] I
2018 Aug 03
2
rsync versioning problem
I seem to have an rsync versioning problem. The sender is an old ClearOS6 server with rsynv 3.0.6 The receiver is a brand new Centos7-armv7 server with rsync 3.1.2 I am running rsync over ssh Got the error: rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6] And researching this it comes down to a versioning issue.? But all I have found was to upgrade the
2015 Sep 04
1
further testing - Re: dhcp errors - Re: dhcp example
This will be it for tonight... Sep 3 20:35:30 homebase dhcpd: DHCPDISCOVER from 02:97:09:02:23:a2 (cubieboard2) via eth0 Sep 3 20:35:31 homebase dhcpd: DHCPOFFER on 192.168.192.21 to 02:97:09:02:23:a2 (cubieboard2) via eth0 Sep 3 20:35:31 homebase dhcpd: /usr/local/sbin/dhcp-dyndns.sh: line 17: /var/log/dyndns.log: Permission denied Sep 3 20:35:31 homebase dhcpd:
2015 Sep 07
5
BIND DLZ zone transfers
I am looking at: https://wiki.samba.org/index.php/DNS_administration I am using bind 9.9 on all my DNS servers. To set up secondarying my Samba DNS zones to my other Bind servers. I come across the following: https://bugzilla.samba.org/show_bug.cgi?id=9634 Is it possible to transfer the DLZ zones now as dates on this bug are 2 years old?
2015 Sep 07
8
rsync question
I am trying to rsync the named files under /etc for backup purposes. I tried: rsync -ah --stats --delete -e "ssh -p613 -l root" 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc The stats shows it sees all the files, but only moves the dir /etc/named and the files within it. It does not move the /etc/name* files (like /etc/named.conf). By file count, it is
2015 Sep 03
2
dhcp example
dhcp is working. but what does this mean: Sep 03 15:58:44 homebase.home.htt dhcpd[22993]: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file ??? On 09/03/2015 02:43 PM, Rowland Penny wrote: > On 03/09/15 19:28, Robert Moskowitz wrote: >> >> >> On 09/03/2015 02:17 PM, Rowland Penny wrote: >>> On 03/09/15 19:05,
2015 Aug 28
2
More on bind_dlz - documentation I have not found
In the shower this morning, I realized that samba's dlz is through its ldap interface, probably through dhcp. :) All of that work researching how to set up a dlz database for naught. This is NOT documented in either: https://wiki.samba.org/index.php/DNS or https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD I have not yet checked any ldap documentation on the wiki to
2015 Sep 03
2
dhcp example
On 09/03/2015 04:14 PM, Reindl Harald wrote: > > > Am 03.09.2015 um 22:09 schrieb Robert Moskowitz: >> dhcp is working. but what does this mean: >> >> Sep 03 15:58:44 homebase.home.htt dhcpd[22993]: Not searching LDAP since >> ldap-server, ldap-port and ldap-base-dn were not specified in the config >> file > > what it says - nothing in 99.9% of all
2015 Sep 11
2
rsync question
On 09/10/15, Robert Moskowitz wrote: --------------- Quoted text ------------------ SSh is not parsing the port the way http does, it seems: $ rsync -ah --stats root at 192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: