similar to: samba Digest, Vol 112, Issue 3

Solved: Seems that, as long as you put the "Login script" in the correct place under the Sysvol volume, in AD it needs to be specified as JUST the name of the script. (You know, the irony of working with all this wonderful Samba4 stuff is that I actually end up having to learn more about administering WINDOWS! Sheesh! ;-) On Tue, Apr 3, 2012 at 12:23 PM, Charles Tryon

This seems like such an easy thing, I must be missing something obvious... :-( I'm working on migrating a domain from S2 to S4 and running the samba_tool script. All my users are coming across fine (though I'm not sure why all the old system accounts like "ssh" and "daemon" and "halt" are getting created... another issue). I am using a FreeNAS appliance

I'm not sure if this is an LDAP issue, a Samba issue, a BSD issue or a FreeNAS issue... I'm working at migrating a large block of file shares from an aging CentOS/Samba 3.0.9 server to a FreeNAS (8.0.2) server. (The FreeNAS box is running FreeBSD 8.2-RELEASE-p3 and Samba 3.5.11.) I will eventually be migrating the entire domain and user base off of that server, but for the time being, I

Le 25/10/2009 01:23, openssh-unix-dev-request at mindrot.org a ?crit : > Date: Sat, 24 Oct 2009 16:15:05 -0700 > From: Dave Yost<Dave at Yost.com> > To:"openssh-unix-dev at mindrot.org" <openssh-unix-dev at mindrot.org> > Subject: known_hosts(5) man page > Message-ID:<pdy98830624081ac70939292f43@[192.168.1.2]> > Content-Type: text/plain;

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags. While looking at /var/log/messages I also see this when starting

I have been doing some work with the new Samba4 version and have some questions. Is this the right list to ask on, or is there a development list that would be better? (I am currently following the Samba4 HOWTO Wiki at: http://wiki.samba.org/index.php/Samba4/HOWTO, and building from the "git" repository. The system seems to be working well, but I have some questions about migrating

Hi Team, Trying to upgrade samba 4.9.3 on debian wheezy. while building facing the following error. Build phase! ` Configuring Samba 4 - x86_64 Checking for program gcc or cc : /usr/bin/gcc Checking for program cpp : not found Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for gcc

Hello Charles and Douglas, I really believe that BZ2200-BR model is the same as mine BZ1200-BR, with different capacity. If you see the BZ2200-BR specs you will notice the manufacturer "APC-Microsol". Those no-breaks have a USB port in it, but in fact it is a serial<->usb cable, usually uses the port "/dev/cuaU0". In mine, the serial<->usb chip is from FTDI, and

nothing appens. The output is exactly the same as below (attached screen with freenas config) [image: Immagine in linea 2] 2014-04-03 13:16 GMT+02:00 Charles Lepple <clepple at gmail.com>: > please reply to the list. thanks! > > See below. > > On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > > thanks for your reply.* I'm running the latest version of

I've been using one Samba4 server based on a Fedora14 distro, but because of my continuing issues with Bind 9.7 and dynamic DNS updates, I'm trying to move to a Fedora 16 base, which includes Bind 9.8 by default (not to mention a bucketload of other updates). My question: What is the best way to pull the current domain data from the first server to the second one? In particular, I'm

Gabor: note, these HCL reports go to the nut-upsdev list. Begin forwarded message: > From: Gabor Tjong A Hung > Subject: Re: Network UPS Tools - Compatibility List > Date: September 3, 2013 2:18:31 PM EDT > > Sorry, > I just noticed the "If your device isn?t listed" part: > > [HCL] Forza FX-1500LCD supported by blazer_usb > > > [root at freenas] ~#

please reply to the list. thanks! See below. On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > thanks for your reply. I'm running the latest version of FreeNAS based on 9.2 with NUT 2.7.1 > > [root at archivio ~]# uname -a > FreeBSD archivio.dannyb78.home 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+ > 38751c8: Thu

----- Forwarded message from Josh Paetzel <josh at ixsystems.com> ----- From: Josh Paetzel <josh at ixsystems.com> Date: Fri, 26 Oct 2012 09:55:22 -0700 To: freenas-announce at lists.sourceforge.net Subject: [Freenas-announce] FreeNAS 8.3.0-RELEASE User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi all, Sorry for the delay - three business trips abroad and LOTS of head scratching with USB Keys and DVD's of SuSE and FreeBSD... The question about the USB reports from Windows is still unanswered (I am abroad again !), but *think* the Liebert driver had been stopped. I can report the following updates for my linux setups; SuSE/FreeBSD/FreeNAS [remember here I am trying to make nut

On 30/11/15 10:01, Lars Hanke wrote: > For some reason my secondary DC loses sync every once in a while. It > looks like this in samba-tool drs showrepl: > > Last attempt @ Thu Nov 19 13:53:09 2015 CET failed, result 5 > (WERR_ACCESS_DENIED) > 229 consecutive failure(s). > Last success @ Wed Nov 18 18:48:07 2015 CET > > Restarting samba fixes the issue for an

For some reason my secondary DC loses sync every once in a while. It looks like this in samba-tool drs showrepl: Last attempt @ Thu Nov 19 13:53:09 2015 CET failed, result 5 (WERR_ACCESS_DENIED) 229 consecutive failure(s). Last success @ Wed Nov 18 18:48:07 2015 CET Restarting samba fixes the issue for an unpredictable time. Sometimes hours, sometimes many weeks. So I wrote a script to

On 2/5/2014 8:24 AM, Charles Lepple wrote: > On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > >> NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS > Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have

On Aug 18, 2013, at 12:14 AM, Lyndon Drake wrote: > I'm happy to test an updated build, but have no idea about how to go about doing a build in the first place. Could someone help me in the process of creating a snapshot build for FreeNAS? I am not familiar with the specifics of building for FreeNAS, but our BuildBot instance is making source snapshots again:

I missed that snmp-ups set pollfreq to 30 by default. I'd hope that it would set deadtime to an appropriate value as well than, no? Is there a way to query what the settings are or what the defaults are? I'm going to set POLLFREQ=30 and DEADTIME = 90 and see if that has any effect. I'll check for the logs. And if that doesn't get my anywhere I'll look at trying to simulate

On 30/11/15 12:35, Lars Hanke wrote: > Thanks Rowland, for the thoughts. > > > If you are running Samba4 as an AD DC, you should never start the nmbd > > deamon, you should also never start smbd manually. > > Yes, I could optimize to use /etc/init.d/samba-ad-dc immediately,but > in fact this is what /etc/init.d/samba does. The messages with "AD DC >