similar to: problem with sessions

Hi again. the users work usually in this way, browsing the network to find a serverdc using \\serverdc on explorer file. and after that them choose the correct share and working on inside with their files need it. someone set that share as mapped unit with letter Z or Y. but they normally work in this way daily. so, i can't set browseable = No because the users need to be see the shares on

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

On Wed, 1 Mar 2017 17:48:47 +0100 Tony Peña <emperor.cu at gmail.com> wrote: > server role = dc > server role = active directory domain controller > i'm correct ? Nearly, but you should only have one 'server role' line and the second line is the correct one. > > ---- > > on include shares.conf is all share directorys...i got 47 shares... > so

Hi, We have some issue with the reverse DNS in Samba AD. We're running Bind9_DLZ on Ubuntu 18.04. The DHCP server(Ubuntu 16.04) is different to the AD server and not in the same AD domain. The DHCP scope points to the Samba AD server as the DNS server When a machine with DHCP assigned address tries to update the DNS record, it is able to update the forward zone but not the reverse zone. The

On Thu, 2 Mar 2017 18:48:47 +0100 Tony Peña <emperor.cu at gmail.com> wrote: > hi Rowland, > > ok a refix the other lines above but.. > > what means "I think your problem is down to your DNS setup, it seems > to be using > flatfiles" and this is NOT supported by Samba. > > > OK, you have things like this in your bind conf files: zone

Hai, You posted the correct things here, for a quick fix i I'm buzzy with something else atm but i saw that /dev/urandom part. Add in the bind9 (named) apparmor profile # Samba DLZ /{usr/,}lib/@{multiarch}/samba/bind9/*.so rm, /{usr/,}lib/@{multiarch}/samba/gensec/*.so rm, /{usr/,}lib/@{multiarch}/samba/ldb/*.so rm, /{usr/,}lib/@{multiarch}/ldb/modules/ldb/*.so rm,

On Wed, 1 Mar 2017 16:24:36 +0100 Tony Peña <emperor.cu at gmail.com> wrote: > Hi thanks by answer quickly > > yes is a ad pdc, i refers to PDC i think will be the same, now i saw > isn't. anyway, this is the smb.conf and krb5.conf I suggest you change your smb.conf to: [global] workgroup = sambadc realm = SAMBADC.LCL netbios name = samba-dc server string

Hi Denis & Rowland Thanks for the suggestion to trim the smb.conf after which the DC-1 is connecting to the Windows Server 2008 shared folder smbclient -k //IUMSVRAPP01/Pastel12 -d 9 and DC-2 is also connecting after using the DNS name of the Windows server. *You'd better switch your DNS to Bind-DLZ. Internal DNS is not that good for larger site (looking at your DNS domain name, I guess

Hello all. I'm having a problem debugging an IVR I'm building. I can't see any reason this shouldn't be working. Firstly the asterisk version is: Asterisk SVN-trunk-r7230 built by root @ localhost.localdomain on a i686 running Linux on 2006-02-17 22:44:48 UTC Basically the problem is this. While the playbacks are happening you can push any one of the options and to happily

Hi Denis I have upgraded my samba DC-1 from 4.6.12 to 4.7.4 which has solved the replication issues between DC-1 and DC-2. Now both the DC's are running on 4.7.4. Like Rowland said previously, you should remove all RODC that have been installed prior to Samba 4.7. There are many fixes that have been added since 4.6. Before I remove my RODC's I like to clear out few doubts: 1. Instead of

I'm working on an IVR that gives the users the option (number 5 in the main menu) to dial by extension: exten => 5,1,Set(TIMEOUT(digit)=5) ; Dial Extension exten => 5,2,Set(TIMEOUT(response)=10) exten => 5,3,Background(LCL/prompt-60) exten => 5,4,WaitExten(15) When going option 5 you can dial some extensions such as 2802, it goes to the extension (all extens start with 28 on the

On 06/08/2019 16:21, L.P.H. van Belle via samba wrote: > Its pretty clear how in the wiki. > > https://wiki.samba.org/index.php/DNS_Administration > > samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa > > ;-) And that would get you a /24 network And I also thought wrong, yes the name is wrong, but it should have been '11.0'

Javier Fernández-Sanguino Peña has discovered an exploitable vulnerability in the way that Shorewall handles temporary files and directories. The vulnerability can allow a non-root user to cause arbitrary files on the system to be overwritten. LEAF Bering and Bering uClibc users are generally not at risk due to the fact that LEAF boxes do not typically allow logins by non-root users. For 2.0

I have read that so many times. I started out with the simple, prompted 'samba-tool domain join' and built up from there. Version is: Samba 4.7.6 from Ubuntu (18.04.2) Interesting what happens when I take out --site directive (see below). root at DC2:~# samba-tool domain join DOMAIN1.DOMAIN DC --username='DOMAIN1\EnterpriseAdminUser' --realm='DOMAIN1.DOMAIN'

Samba 4.1.16, Centos 6.6 x86-64, BIND_DLZ 9.9. I have three AD DC's that were functioning normally. However, today I restarted BIND on one node, and it failed to start with this message in the log (names changed): May 10 07:02:49 benford named[6767]: Loading 'AD DNS Zone' using driver dlopen May 10 07:02:49 benford named[6767]: samba_dlz: started for DN DC=samdom,DC=example,DC=com May

Yes, offcourse, the 172.19 is a "bad" example. I suggest we use the official RFC 1918 zones. 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 And for example 192.168.0.0/24 as extra, or people get confused. ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: woensdag 7

Hai,   Seeing : > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable > zone '168.192.in-addr.arpa' > Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no > NS records > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone > 'local.laurenz.ws'   Normaly you should see first the local.laurenz.ws

How is the reversed domain handled, or is it not. Rowland, you did not have that in your sample you cobbled together. In /usr/share/samba/setup/named.conf there is: zone "123.168.192.in-addr.arpa" in { type master; file "123.168.192.in-addr.arpa.zone"; update-policy { grant ${REALM_WC} wildcard *.123.168.192.in-addr.arpa. PTR;

On Sun, 10 May 2015, Rowland Penny wrote: > can you post your named conf files. Sure. This is samba's: dlz "AD DNS Zone" { database "dlopen /mnt/domain/samba/europa/lib/bind9/dlz_bind9_9.so"; }; and this is BIND's (notice the last line commented out): options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db";

Ok, new test. Besides that i dont like the python errors shown, this still looks good. So i dont know.. See below, i can not make it error. for x in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do samba-tool dns add dc1.internal.dom.tld $x.249.10.in-addr.arpa 158 PTR host-test.extrazone.dom.tld ; done Record added successfully Record added successfully Record added successfully Record added