similar to: Compiling Samba 4.0.7 - make test results

Hi, I thought Samba4 was able to do everything what was doing Samba3. According to that isn't it possible for you to add a new DC into your NT4 domain which runs Samba4? As it is a DC in addition to others DC (those running Samba3) your domain should continue to work as it did for years. You would just get another DC running more recent Samba. I expect that Samba4 as filesrv is able to

Wow, this is great. However, we need to use DNS. If we enable it AFTER the computer has joined the domain, would it keep working, or DNS is no avail in W8.1? D?a 15.04.2015 o 22:03 James Fromm nap?sal(a): > That worked. Server joined just fine. Thanks Robert! > > Thanks, > James > > On 04/15/2015 12:48 PM, Robert Moulton wrote: >> James Fromm wrote on 4/15/15 12:45 PM:

I have tested the patch against 4.3.1 compiled from sources but it does not seem to work. Either I did something wrong while compiling, or the patch dosen't fix the problem. ERROR(<type 'exceptions.ValueError'>): uncaught exception - unable to parse dn string File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return

On 04/20/2016 5:22 AM, Mgr. Peter Tuharsky wrote: > Hallo > > The Debian team was unable to keep 4.1.17 patched, so they switched to > 4.2 branch. However, fileserver at this version (4.2.10) is no more able > to communicate with DC at samba 3.5 (unable to authenticate users - got > weird rpc version error in log) > > Please, are there any parameters that could make this

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mgr. > Peter Tuharsky via samba > Verzonden: woensdag 20 februari 2019 10:28 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba + BIND9 DLZ. DNS dosen't resolve > FQDN, only short hostname > > Well, the mystery is solved. It WAS Avahi, in a way...

Hello, I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite sympathetic UPS, I must say from first glance. I have made a proper serial cable (btw i hate all those constructor's decisions to make distinct serial wiring for each and every UPS type from each and every manufacturer!) I use [tripplite] driver for NUT and I can use upsc to get report from UPS, but

On Fri, 25 Aug 2017 16:03:08 +0200 "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > Rowland, > > > I'm following this thread because I'm trying to use Linux member > server (Debian 9) and use Windows AD users in Linux (filesystem etc). > > It seems I have working Kerberos and to a degree, Winbind too, > because both > >

On Fri, 30 Jun 2017 10:09:16 +0200 "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > Hi all, > > I have W2k8 AD and I need to join Samba fileserver. > > Since I'm new to the topic, I'm following a howto, and it says I must > first make Kerberos authenticate users and only then start configuring > Samba. But I cannot get over the

This command lists all directories in iss_num. However the . (iss_num itself) has drwxrwxr-x Now for the incriminating file example that shows abnormal ACL in Windows: the file resides in iss_num/am/uz and has -rwxrwxrwx So there is no + in listing for share directory nor for files in the directory structure. Peter D?a 10.03.2015 o 10:37 Rowland Penny nap?sal(a): > On 10/03/15 07:16, Mgr.

Rowland, thank You, but this removes only the NS record, but the faulty domain A records remain. How to deal with them, I don't know. They behave unlike the ordinary A records. Name=, Records=8, Children=0     SOA: serial=27, refresh=900, retry=600, expire=86400, minttl=3600, ns=blacktux.interbronz.local., email=hostmaster.interbronz.local. (flags=600000f0, serial=27, ttl=3600)     NS:

Hm, it is quite large. I will snip all comments out and all shares that are not interesting smb.conf: [global] workgroup = ldap1.sk server string = server %L wins support = no dns proxy = no netbios aliases = datastore dokumenty iss pravo prenos matriky log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d

Charles, maybe we are getting closer :-) > The tripplite_serial_protocol branch has some debug statements that will show up if you run "sudo drivers/tripplite -D -a name-of-ups" from the nut directory. Network UPS Tools - Tripp-Lite SmartUPS driver 0.91 (2.7.4-432-gafd90f5a) ?? 0.000000??? [D1] debug level is '1' ?? 0.177766??? [D1] W value = 0x86 ?? 0.177782??? [D1] L

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

On 10/03/15 10:01, Rowland Penny wrote: > On 10/03/15 09:51, Mgr. Peter Tuharsky wrote: >> This command lists all directories in iss_num. However the . (iss_num >> itself) has drwxrwxr-x >> >> Now for the incriminating file example that shows abnormal ACL in >> Windows: the file resides in iss_num/am/uz and has -rwxrwxrwx >> >> So there is no + in

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the

On Thu, 24 Aug 2017 12:26:11 +0000 "A. James Lewis" <james at fsck.co.uk> wrote: > Well, network connectivity to the other DC would probably also be > required... and I don't have that currently... so there's the first > hurdle... but thanks for confirming that there's no other > configuration required. > > I'm slightly surprised that the

Hello, We're having a problem with "Samba 4" joined to a "Server 2008 R2" domain (at "Server 2008" functional level across the forest). The interesting thing is that this only affects a single user - all other accounts work without problems. When accessing our main server using that account, "smbd" always reports "can't parse the PAC:

Hallo, we have Samba 3 domain w/LDAP backend. Recently we have set up Samba 4.1.7 fileserver, a member of the domain, as a first step of full migration to Samba 4. Now, we have problem with file ACL on the Samba4 fileserver. Linux ext4 fs has 777 ACLs for the file. Why does it look like in Windows (both XP and 2k8r2) that "Everyone" has not write permission? Sincerely Peter

Well, finally I found the recommendations against .local here: https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ However, still, the originating wiki should AFAIK be more verbose. https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller For now it only says "Make sure that you provision the AD using a DNS domain that will not need to be

Hm, I thought this to be the very TLD that is specifically assigned for local networks with no plans to become Internet-wide. What is the recommended TLD for such networks then? Dňa 20. 2. 2019 o 11:33 Rowland Penny via samba napísal(a): > On Wed, 20 Feb 2019 11:17:05 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> Hai, >>