Displaying 20 results from an estimated 6000 matches similar to: "preparing to upgrade 4.6.7 to current"
2018 Aug 21
0
Louis' Debian install notes
Louis,
Glad to see you back.
I asked this question about the time you left for family matter (hope
family is fine, now.)
Perhaps you could locate this dependency list that was in one of your
install instruction text file, previously posted on one of your file sites?
(If my memory serves me, it was a text file instruction for install of
Samba 4.7 or 4.6, maybe?)
On Fri, Aug 3, 2018 at 6:15
2018 Mar 09
2
Demoted dc not completely demoted, maybe?
So, for now, should I work my way through the DNS manager and delete any
references for the old dc manually or just leave it alone?
On Thu, Mar 8, 2018 at 6:16 PM, Andrew Bartlett <abartlet at samba.org> wrote:
> On Thu, 2018-03-08 at 17:49 -0600, Robert Wooden via samba wrote:
> > Will these DNS listings clear themselves with time or do I have a problem
> > here?
>
>
2018 Aug 23
1
Louis' Debian install notes
Hai Bob,
Thanks, yeah the family is getting better, 2 funerals in 1 month is hard.
But we get through that, its in the end, this happens to everybody...
I think you did mean https://github.com/thctlo/samba4
Most can be found there.
The howto's are based on debian stretch samba 4.5, these work fine also for 4.7 and 4.8.
But you need to update the smb.conf a bit for that.
Greetz,
2018 Mar 09
2
Demoted dc not completely demoted, maybe?
I Google searched this morning and had found this: "
https://superuser.com/questions/1281015/changing-computer-name-on-dns-samba4-ad-server"
which discusses a similarity to your suggestion.
I was concerned because I cannot tell if the OP is referencing 'internal
dns' or 'bind9'. However, what the OP is talking about doing, makes sense.
(Could be later today before I
2018 Mar 09
0
Demoted dc not completely demoted, maybe?
On Thu, 2018-03-08 at 19:02 -0600, Robert Wooden via samba wrote:
> So, for now, should I work my way through the DNS manager and delete any
> references for the old dc manually or just leave it alone?
Yes, clean it up by hand. Except the SOA, which you can change to
something else if you like.
> On Thu, Mar 8, 2018 at 6:16 PM, Andrew Bartlett <abartlet at samba.org> wrote:
>
2018 Feb 25
0
preparing to upgrade 4.6.7 to current
I am preparing to upgrade from 4.6.7 (from source) to current 4.7.5.
I have completed other version upgrades in the past and have not
experienced this event. I have two (2) DC running as domain controllers
properly replicating each to each other.
On the (non-FSMO) DC I ran this to check the db and got:
root at dc07:~# samba-tool dbcheck --cross-ncs
Checking 3546 objects
NOTE: old (due to rename
2015 Feb 25
1
samba4 domain member and multiple domains
Was busy, jumped back on here and answers Rowland's post (I think he
might be into something there) and overlooked your post.
No, I haven't but, I will, soon.
---
-------------------------
Bob Wooden of Donelson Trophy
615.885.2846 (main)
www.donelsontrophy.com [3]
"Everyone deserves an award!!"
On 2015-02-25 16:18, Miguel Medalha wrote:
>> I've got a samba4
2018 Mar 09
2
Demoted dc not completely demoted, maybe?
The "DNS_TYPE_NS" records show the correct DC's (both, I have two).
The "DNS_TYPE_A" records show the correct DC's ip addresses.
The "DNS_TYPE_SOA" shows the demoed DC FQDN in the "mname"
> It should produce the SOA record (after you make the obvious changes),
> what 'dnsRecord' objects does it show ? There should a
2017 Nov 24
0
administrator does not have permission
In the Windows world side when an "administrator" cannot 'take ownership'
of a file share, the docs discuss the "System" account being used as it
(System account) has greater permissions than that of the administrator.
I remembered reading this page https://wiki.samba.org/index.
php/The_SYSTEM_Account and have now re-read said page *carefully*.
There I find this
2015 Feb 08
0
ERROR_DNS_UPDATE_FAILED and NT_STATUS_UNSUCCESSFUL
Okay!!! My member server ip address is 192.168.**.56 (static).
When I run your command it is reporting the ip address of 192.168.**.55
(which is my DC02 address.)
So, I need to correct this. How do I remove the 'old member server' ip
address 192.168.**.55 reference and correct to 192.168.**.56?
---
-------------------------
Bob Wooden of Donelson Trophy
615.885.2846 (main)
2015 Jan 08
0
getting permissions denied on home folders
Part of the smb.conf
[home]
path = /home/samba/DTDC01/users
comment = user folder 4 redirection
read only = no
Hum-m-m?
---
-------------------------
Bob Wooden of Donelson Trophy
615.885.2846 (main)
www.donelsontrophy.com [1]
"Everyone deserves an award!!"
On 2015-01-08 12:56, Rowland Penny wrote:
> On 08/01/15 18:37, Bob of Donelson Trophy wrote:
> First, I keep
2015 Jul 24
1
cannot update apt-get
You are correct. I discovered (a few minutes ago) that
/etc/apt/sources.list.d/debian-wheezy-sernet.list had the duplicate line
within it.
Funny thing was, when I "comment out" the duplicate line, that
"commented out" the single entry within the file. All other lines were
already 'commented out'. So, after 'apt-get update' ran without error, I
went back and
2015 Feb 13
0
SOLVED Re: ntpq -p ***Request timed out
On 13/02/15 19:48, Bob of Donelson Trophy wrote:
>
>
> Thank you, Rowland.
>
> Copied your simpler ntp.conf file into my member server. Made the
> appropriate changes. Restarted all the ntp service on all machines (just
> in case.) Ran 'ntpq -p' (on member server) and got the correct answer.
> Proper connection to DC's.
> ---
>
>
2014 Dec 08
0
Fwd: Installing EnterpriseSamba (Sernet-samba) on Ubuntu
and you didnt find my scripts ;-)
https://secure.bazuin.nl/scripts/
The wheezy scripts should work also on ubuntu.
It all in there what you want to know.
Greetz,
Louis
>-----Oorspronkelijk bericht-----
>Van: bob at donelsontrophy.net
>[mailto:samba-bounces at lists.samba.org] Namens Donelson Trophy
>Verzonden: zondag 7 december 2014 16:41
>Aan: SAMBA MailList
2015 Apr 24
0
samba-check-db-script python failure
Hai Bob.
SETDNSDOMAIN='hostname -d'
needs to be:
SETDNSDOMAIN=`hostname -d`
.. so change them all .
SETDNSDOMAIN=`hostname -d`
SETHOSTNAME=`hostname -s`
SERVER_IP_ADDRESS=`hostname -i`
and you can ignore :
>[....] Stopping domain name service...: bind9rndc: connect failed:
>127.0.0.1#953: connection refused
>
>. ok
>
>[ ok ] Starting domain name service...:
2015 Jan 29
0
Fwd: Re: W7 client cannot adjust file permissions via ADUC
First, I will try forwarding the original sent this morning.
If it still appear poorly formated I'll try something different.
PLEASE WAIT FOR A CLEAN COPY IF THIS ONE IS STILL BAD.
---
-------------------------
Bob Wooden of Donelson Trophy
615.885.2846 (main)
www.donelsontrophy.com [1]
"Everyone deserves an award!!"
-------- Original Message --------
SUBJECT:
Re:
2015 Feb 27
0
NT_STATUS_CONNECTION_REFUSED, again!!!
On 27/02/15 20:08, Bob of Donelson Trophy wrote:
>
>
> No.
>
> What I did was change the first few to see what happens. And still the
> first 13 (this time, last time 17) failed. I am baffled why the first 11
> to 17 fail (randomly) and the remainder receive "Successfully granted
> rights."
>
> ---
>
> -------------------------
>
> Bob Wooden
2015 Jan 28
2
W7 client cannot adjust file permissions via ADUC
That was a cut/paste error.
I've been thinking (danger, danger) when I test kerberos it returns the
two DC's are available. Should it be including the member server also?
Didn't I see the script setup kerberos on the member server? (Remember
this was installed with the gen one scripts, not the newest scripts.)
---
-------------------------
Bob Wooden of Donelson Trophy
2015 Jan 08
1
getting permissions denied on home folders
On 08/01/15 19:10, Bob of Donelson Trophy wrote:
>
>
> Part of the smb.conf
>
> [home]
> path = /home/samba/DTDC01/users
> comment = user folder 4 redirection
> read only = no
>
> Hum-m-m?
>
> ---
>
> -------------------------
>
> Bob Wooden of Donelson Trophy
>
> 615.885.2846 (main)
> www.donelsontrophy.com [1]
>
>
2015 Jun 25
0
add rsync -A -X to Backuppc "RsyncArgs" get 'Got fatal error during xfer (fileListReceive failed)'
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The command line order shouldn't matter though that might depend on
what else is in there (especially -s).
Rsync is backwards compatible so the version mismatch shouldn't matter
but 3.1 has some nice benefits over 3.0.9 so upgrading is a good idea.
In the end you probably need to know what rsync command line is being
run and what rsync says