similar to: Won't execute LOGON.CMD?

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

---------- Forwarded message ---------- From: Charles Tryon <charles.tryon at gmail.com> To: Samba list <samba at lists.samba.org> Cc: Date: Tue, 3 Apr 2012 12:23:54 -0400 Subject: [Samba] Won't execute LOGON.CMD? 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.

(Posted to Samba-technical, but probably should have cross posted here for people interested in Samba4...) I have created a Samba4 Project Status Wiki page at: https://wiki.samba.org/index.php/Samba4/Status. Actually, the "Status" page was already there, but hadn't been updated since about 2008. Hopefully, we can do better! The page is currently in a very preliminary state, with

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

----- 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 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 I have usrmgr.exe (form NT server ver.5.1) to manage user accounts of samba.(one year ago) I set logon hours from 8:00 to 16:00. My server (Fedora 7) changed the time correctly from winter to sumer (+ 1 hour). I chenged hardware time clock -w (write system clock to hardware clock synchro). But users cant' login at 8:00 morning !!!! I must back logon hours one hour back in usrmgr

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

Hello everyone I have configured samba4 as per the details prived on samba how to homepage. Now i can successfully add my windows XP and windows 7 machine to the domain. I logged in to windows XP machine as domain administrator and created a user using dsa.msc The user is able to login on windows XP machine but when I tried to login on windows 7 this is the error which I get The trust

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 >

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 daemon" are generated by that script, and it is the failing one. > What

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, I have a weird problem with RSync: On a NAS are about 1,2 TB data. When I plug in a harddisk and make a backup with RSync, "df -h" shows the backup disk filling up to nearly 1,2 TB. But after RSync has finished, there are only 3.7 GB on the backup disk. System: Linux nas 2.6.37-gentoo-r4 #1 SMP Tue May 3 19:54:31 CEST 2011 x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel

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

Greetings! I''ve got a FreeBSD-based (FreeNAS) appliance running as an HVM DomU. Dom0 is Debian Squeeze on an AMD990 chipset system with IOMMU enabled. The DomU sees six physical drives: one of them is a USB stick that I''ve passed through in its entirety as a block device. The other five are SATA drives attached to a controller that I''ve handed to the DomU with PCI

Hi R-users, I have a question relating to the HoltWinters() function. I am trying to forecast a series using the Holt Winters methodology but I am getting some unusual results. I had previously been using R for Windows version 2.7.2 and have just started using R 2.9.1. While using version 2.7.2 I was getting reasonable results however upon changing versions I found I started to see unusual

> Why bother with all the above, just use samba-ad-dc instead. Yes, I streamlined the script somewhat. Let's see what happens when replication fails next time. > You are going to have to supply more info, is there anything in the logs > when replication fails? > If not, try raising the log level until you do get something. Anything specific I should look for? As said it

I am trying to extract only the winters (defined to be 01-Dec through 28-Feb) of daily data from 1948-2002. There are 90 days in each winter season. I wrote the following code to gather the winter dates into a single vector: DJF <- NULL for(year in 1949:1999) { temp.begin <- strptime(paste("01/12", year-1, sep="/"), "%d/%m/%Y") temp.end <-

Opensolaris this ain''t, but zfs-related nevertheless. ----- Forwarded message from Josh Paetzel <josh at ixsystems.com> ----- From: Josh Paetzel <josh at ixsystems.com> Date: Fri, 13 Jul 2012 12:01:24 -0700 To: freenas-announce at lists.sourceforge.net Subject: [Freenas-announce] FreeNAS 8.2.0-RC1 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506