Displaying 20 results from an estimated 20000 matches similar to: "Best practice multi-homed AD DC"
2020 May 17
3
Best practice multi-homed AD DC
On Sun, May 17, 2020 at 1:43 PM Rowland penny via samba <
samba at lists.samba.org> wrote:
> On 17/05/2020 19:30, Johannes Engel via samba wrote:
> > Dear all,
> >
> > as I am currently planning a network with Samba AD DC I was wondering if
> > you can recommend any best practice for a multi-homed AD DC.
>
> Best practise is: do not multi-home a DC.
>
2020 May 17
0
Best practice multi-homed AD DC
On 17/05/2020 19:30, Johannes Engel via samba wrote:
> Dear all,
>
> as I am currently planning a network with Samba AD DC I was wondering if
> you can recommend any best practice for a multi-homed AD DC.
Best practise is: do not multi-home a DC.
Rowland
2020 May 18
1
Best practice multi-homed AD DC
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Michael Jones via samba
> Verzonden: maandag 18 mei 2020 11:34
> Aan: Rowland penny
> CC: sambalist
> Onderwerp: Re: [Samba] Best practice multi-homed AD DC
>
> On Mon, May 18, 2020 at 2:44 AM Rowland penny via samba <
> samba at lists.samba.org> wrote:
>
2020 May 18
1
Best practice multi-homed AD DC
On Mon, May 18, 2020 at 2:44 AM Rowland penny via samba <
samba at lists.samba.org> wrote:
> On 17/05/2020 23:10, Michael Jones wrote:
> > Why?
> Amongst others, you may get:
>
> Slow / Failed logins
> Replication issues
> Group policy access issues
> login script issues
>
> A multi-homed DC (for whatever reason) is a bad idea.
>
> Rowland
>
I
2009 Oct 20
1
[Bug 616] New: Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
http://bugzilla.netfilter.org/show_bug.cgi?id=616
Summary: Duplicate rules for multi-homed hostnames. IPv4 and IPv6
inconsistent treatment.
Product: iptables
Version: unspecified
Platform: i386
OS/Version: All
Status: NEW
Severity: minor
Priority: P4
Component: iptables
2019 Nov 03
2
DC with outdated secrets
Dear list,
by mistake some script (msktutil) has updated machine password and keytab
for one of my DCs (samba-4.10.10). While I could restore the keytab
(/var/lib/samba/private/secrets.keytab) using samba-tool domain
exportkeytab, I fail to come up with a way to update the secrets file
(/var/lib/samba/private/secrets.ldb) with a new machine password.
Can you please help me with an idea how to fix
2024 May 08
3
Wiki - Best Practise to install a 2nd AD-DC or "backup"-DC
Hello list,
I searched the wiki, but couldn't find any article on this topic - maybe
I used the wrong terms ...
Is there a "Best Practise" documentation how to install a 2nd AD-DC (or
"backup"-DC)?
Cheers,
Torsten
2006 Dec 20
6
select lists - DB best practice
Hey guys,
I''m putting together an app with user profiles, and each user will be
able to update a section called ''quick stats''.
This will involve lots of drop down lists with options like ''hair
colour'', ''height'', ''Location'' etc etc.
The way I m thinking about doing it is to create new table for each
group of options
2024 May 08
1
Wiki - Best Practise to install a 2nd AD-DC or "backup"-DC
On Wed, 8 May 2024 09:48:48 +0200
lists--- via samba <samba at lists.samba.org> wrote:
> Hello list,
>
> I searched the wiki, but couldn't find any article on this topic -
> maybe I used the wrong terms ...
>
> Is there a "Best Practise" documentation how to install a 2nd AD-DC
> (or "backup"-DC)?
>
> Cheers,
> Torsten
>
That
2008 Oct 14
1
GSSAPI Key Exchange on multi-homed host
>From a security standpoint, if the default keytab (/etc/krb5.keytab)
contains only ONE principal, does it matter if GSSAPIStrictAcceptorCheck
is set to "yes" or "no"?
My company uses an internally built OpenSSH package that includes the
GSSAPI Key Exchange patch. Because we have 1000s of hosts, we need to use
a "standard" sshd_config file that works for the
2013 Jul 31
3
Multi-homed SIP in Asterisk 11?
Most of my experience until recently has been in Asterisk 1.2, and I am
just starting to make use of Asterisk 11 for new systems.
I have a question about using SIP on a multi-homed machine.
I have a customer who wants an Asterisk box with two network interfaces:
one on the public Internet (no NAT), and one on a private LAN. The box
will not do any IP forwarding between interfaces. They want to
2007 Nov 28
3
Asterisk on multi-homed systems
Greetings list,
I remember a discussion many months ago which ISTR concluded that asterisk didn't play nicely at all in multi-homed setups (e.g. SIP packets not being sent out through the same interface they were received on, etc.).
Is this still the case, or are there versions which have resolved the issue? Even if it's still the case, is this only a problem for SIP, or does it affect
2018 Jan 22
5
RODC and LDAP via Simple Authentication fails
Dear all,
setting up a DMZ environment I was thinking to use an RODC there for
user authentication. One of the application in the DMZ needs to access
the directory via LDAP.
When I tried to connect to the RODC using LDAP with simple bind, I
always received the following error
ldap_bind: Invalid credentials (49)
additional info: 80090308: LdapErr: DSID-0C0903A9, comment:
1998 Oct 13
0
Bizarre multi-homed name resolution with nmbd?
Hi,
I connected a multi-homed Win95 machine (carrot, see below) to two
networks (ankh-net and morpork-net) which a multi-homed Linux machine
running Samba 1.9.18p10 (or whatever the latest <2 is) was also connected
to (vimes) and wanted to see which of the two interfaces Win95 would
pick...
--------------------------------- ankh-net 134.225.241.0/24
| |
2017 Nov 08
2
Samba 4.7 DC with BIND9_DLZ and MIT Kerberos fails at DNS Update
On Tuesday, 7 November 2017 21:04:09 CET Marc Muehlfeld wrote:
> Hi Johannes,
>
> Am 07.11.2017 um 18:35 schrieb Johannes Engel via samba:
> > a month ago I have filed bug #13066 about Samba 4.7 DC using BIND9_DLZ
> > as DNS backend failing to run samba_dnsupdate using MIT Kerberos. The
> > logs show a kerberos error "Request is a replay". Logs attached here:
2003 Jul 26
0
Problems with chan_sip on multi-homed hosts
Hey all,
I'm experiencing a problem with chan_sip on a multi-homed machine.
The machine has 1 interface to the rest of the world and 1 interface
on a local network. The local network has public IP-addresses, though,
and the IP-addresses of both interfaces are reachable from the outside
world, but by default, outgoing traffic from that machine to the outside
world will have the IP-address of
2005 May 11
0
Multi-homed faq or docs needed
I tried to implement a multi-homed box using this faq
4.2.1 split access
http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.multiple-links.html
But it says table is invalid. Can someone tell me
what the difference is in Centos? I assume the FAQ is
leaving out how to add tables to the iproute files?
I am trying to have eth0 and eth1 service two
different subnets for apache and not act as a
1998 Nov 18
0
Multi-homed interface name resolution
Hi,
(I think I posted this a few weeks ago, but I haven't found the solution
and had no replies.)
I have a multi-homed server, one interface of which is on the same subnet
as the majority of clients and the other is on a different one (but still
reachable, through a router).
When connecting to the server, it seems to be chance which one of these
interfaces I get.
I believe DNS servers
2020 May 13
0
Multi-homed Samba 4 file server on Samba 4 AD domain - cross network authentication
On 13/05/2020 18:52, David Lomax via samba wrote:
> Hi all,
>
> I have a question about a multi-homed Samba file server and interoperability
> with AD. It's a bit complicated, so please bear with me.
Your problem is probably because your DC knows your Samba ADS client by
its 192.168.42.0/24 Ipaddress.
Also, why only use 10G on part of your network, surely the network speed
2019 Nov 03
2
DC with outdated secrets
On Sun, 2019-11-03 at 16:24 +0100, Johannes Engel via samba wrote:
> 2 hours and I am a little further:
> Helped myself with Andrew's script in source4/scripts/devel/chgtdcpass
> which updated the machine password as well as the keytab.
> After a restart samba keeps complaining now that the (outdated) KVNO 6 is
> no longer part of the secrets.keytab:
> [2019/11/03