similar to: Dual headed DC

On 8/17/18 11:03 AM, Rowland Penny via samba wrote: > I know you say two IP ranges, but are you also thinking of two dns > domains ? No: one DNS domain. > If you are only going to have one dns domain, then it should work, you > will just have to create the required reverse zones and you will > probably be better off using Bind9 instead of the internal dns server. Why? I'm

On Fri, 17 Aug 2018 10:27:39 +0200 Andrea Venturoli via samba <samba at lists.samba.org> wrote: > Hello. > > Perhaps this question is not new, but I found no document on this > (possibly I used the wrong search terms?)... > > Let's suppose I have an AD domain and I need it to work across two > VLANs. My DC will have to IP addresses, 192.168.x.z for one VLAN and

On 8/17/18 11:58 AM, Rowland Penny via samba wrote: > That's a problem to start with, you really are better off with multiple > DC's. I personally would use at least three in your case, one main DC > and another DC in each site. This would ensure that you would have > some fall back if a DC died. Let's for a moment assume: _ this is a test setup; _ my network is very

On Fri, 17 Aug 2018 11:31:01 +0200 Andrea Venturoli via samba <samba at lists.samba.org> wrote: > On 8/17/18 11:03 AM, Rowland Penny via samba wrote: > > > I know you say two IP ranges, but are you also thinking of two dns > > domains ? > > No: one DNS domain. > > > If you are only going to have one dns domain, then it should work, > > you will just

If you want o do it with one DC (not recommended for redundancy), then carry on. Setup the DC as per normal. Ensure that it is listening on both interfaces, and have your clients pointing to it for its DNS server. Assuming the DC is at 192.168.0.2 and 192.168.1.2, both on a /24 subnet, you should have two DHCP servers, and you should be able to hand out a specific DNS server to clients. Then, it

Moved the hdd of my DC over to nicer P4 machine. It started as expected. (I have resolved the eth0 driver issue that happens with Debian/Ubuntu servers when you move a functional hdd to a different machine.) Then I decided to change the static ip address of the DC from 192.168.**.54 to 192.168.**.51. That went as expected, except it seems my W7 client cannot connect to my domain, now. It says

Hello. I've got a Samba server and I'd like it to be master browser and everything else except domain controller (the customers wants a workgroup, not a domain). Lately a Windows 2003 server was added to the net and then I guess it was removed. I keep getting messages like the following in the logs: > Apr 10 03:07:51 apocalypse nmbd[57552]: [2005/04/10 03:07:51, 0]

On 2/17/19 8:18 PM, Rowland Penny via samba wrote: > Possible things to check: > Is the ip for vlan1 10.1.2.34 ? Sure. It's the only IP vlan1 has inside the jail; it's shown as an alias on the base host. > Try just setting 'vlan1' You mean change "interfaces=vlan1 10.1.2.34/24" to just "interfaces=vlan1"? It doesn't change anything (still

________________________________ From: Uday Mhatre<mailto:uday_mhatre at hotmail.com> Sent: ?05-?12-?2014 12:58 To: Andrea Venturoli<mailto:ml at netfence.it> Subject: RE: [Samba] samba 2.2.7a tech issue Just wondering if these samba versions are backward compatible with fedora14 and other Linux distributions. Regards, Uday ________________________________ From: Uday

Hello. Forgive me, but I'm quite new to AD and I've been searching the web for a couple of days, but found nothing relevant... What's exaclty the NSUPDATE option of this port? Is it intended to work with BIND (like the other two in that group)? What are its requirements? Any reference to a tutorial or any other documentation on how to use it? bye & Thanks av.

My actual scenario is: -Hundreds PCs in a internal network (fixed IP), divided in +- 6 different subnets -A +- 6 customers with leased lines -A Cisco Catalyst 4006 connecting groups of PCs to corresponding customers (imagine a Call Center company) -Works fine. The problem: Frequently, it''s necessary to migrate dozens PCs from a customer to another. You know, change all IPs and

Hi, i reduced to one reverse dns zone (192.168.x.x.) same error when converting internal to bind_dlz Jan 23 14:55:39 samba01 named[3279]: Loading 'AD DNS Zone' using driver dlopen Jan 23 14:55:40 samba01 named[3279]: samba_dlz: started for DN DC=local,DC=laurenz,DC=ws Jan 23 14:55:40 samba01 named[3279]: samba_dlz: starting configure Jan 23 14:55:40 samba01 named[3279]: samba_dlz:

Hi, I have solved. I change parameter "listen-on port 53", as follows: From: listen-on port 53 { 192.168.1.20; 127.0.01; }; To: listen-on port 53 { any; }; netstat -lntup | grep 53 tcp 0 0 0.0.0.0:81 0.0.0.0:* OU?A 534/lighttpd tcp 0 0 192.168.1.20:53 0.0.0.0:* OU?A 1930/named tcp 0 0

On 05/04/16 21:28, Rowland penny wrote: >> Choosing NSUPDATE brings in another port/package, named samba-nsupdate >> and described as "nsupdate utility with GSS-TSIG support", which >> installs "/usr/local/bin/samba-nsupdate". > > Is this a BSD thing ? I have heard of the python script 'samba-dnsupdate'. My understanding is that it's a

On Mon, 2017-05-15 at 18:58 +0200, Andrea Venturoli via samba wrote: > On 05/08/17 11:17, Andrea Venturoli wrote: > > Hello. > > > > I've got a network of FreeBSD servers which traditionally hosted a > > classic domain. > > I upgraded some months ago, removing the old PDC and BDC and migrating > > to an AD DC controller in a jail. > > This is

On Mon, July 13, 2020 10:23, Andrea Venturoli wrote: > On 2020-07-13 15:06, James B. Byrne wrote: > >>> Just out of curiosity, are you also using vfs_zfsacl? >> >> Yes. > > But only on DC1, AFAICT! > I see no mention of it on DC2's smb.conf. > That could be the reason why you have two different behaviour. > > bye > av. > That appears to

On 05/03/16 22:55, Rowland penny wrote: > Don't use freebsd, but Samba 4, when run as an AD DC, uses nsupdate to > update a computers DNS records in AD. First off, thanks for answering. Alas, I don't really understand what you mean... Is it used to dynamically add A records for clients that connect to the AD? >> Is it intended to work with BIND (like the other two in

On 7/25/19 6:48 AM, rainer at ultra-secure.de wrote: > Am 2019-07-25 15:41, schrieb hw: >> On 7/25/19 2:53 PM, rainer at ultra-secure.de wrote: >>> Am 2019-07-25 14:51, schrieb hw: >>>> Hi, >>>> >>>> how can DNS reliability, as experienced by clients on the LAN who are >>>> sending queries, be increased? >>>>

Hi all, I've got some problems with vista sp1 + samba 3.0.28a vista will not save the profiles nor load them. ! I'm all familiar with the .V2 thing. vista however does create the "profilename.V2" directory, but does not populate it with the data Xp machines work like a charm however. profiles path's are: \\<server>\profiles\testuser so the problem with the .V2 part is

Hello, We have fairly large computer park ~100 computers and we want to switch to samba. I installed a new Ubuntu 18.04 LTS fully updated installed samba, after AD join the domain part works i can see users computers and the server, the samba machine is a domain controller the problem is the DNS with this much machines i wanted to use the BIND back-end. The existing environment has 5 vlans