similar to: Can't Apply Group ACL

I installed Samba2.0.7 on my FreeBSD 4.1 box and joined an NT domain. It worked perfect until I changed the hostname today. I found that I couldn't chage the machine password if hostname length is 15. The precedure I do is 1. stop samba 2. change hostname to "abcde1234567890" 3. run smbpasswd -j DOM -r DomControl, then I get the following error message. cli_net_auth2: Error

While running configure on samba2.2.4 source on an HP-UX 10.20 OS, I get the following: checking configure summary... ERROR: No locking available. Running Samba would be unsafe configure: error: summary failure. Aborting config What exactly does "No locking available" mean, and is there a workaround? I'm currently running version 1.9.15p8 on the same OS. TIA! Ed Rodgers

Hi all, I've just install samba2.0.7 on server Tru64. We have one printer HP5Si and others HP4 on the network. Using Samba from our Win95 customer we can print correctly to HP4 but to our HP5si we have the file wanted and one blank page and one page indicated "@PJL RDYMSG DISPLAY=" " ". So we want to suppress these pages. Is there anyone who can help me ?

Hi there, Is the gpg FreeBSD port vulnerable to ElGamal signing key disclosure problem? Info: http://lists.gnupg.org/pipermail/gnupg-announce/2003q4/000276.html Thank you, /Dorin. __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/

We used samba 2.0.6 under Redhat 6.1 with W98/NT4 clients without any problems. Now we upgraded one PC with Windows2000. In the beginning everything worked fine. But suddenly there are problems: Browsing a specific subdirectory of a share on the server cause a inmediate crash of W2k with a automatic restart. I upgraded to Samba2.0.7, again W2k crashes. I connect to this subdirectory from a

am exhausted for solving this. using samba2.0.7 and 2.2.5 in 5000 nis/nis+ and win2k domain environment samba member server in domain giving access to nfs home directories everything working smooth since last 3 years lately couple of users unix home directory are not completely listed when seen from windows explorer via samba. permission on unix home direcotry are 755 ( i changed to 777 to

Dear Samba team: I just download SAMBA 2.0.7 from http://samba.gorski.net/samba/ftp/Binary_Packages/redhat/ and I have already installed SAMBA 2.0.6 which come with my red head linux 6.2 CD. But the 2.0.7 SAMBA is conflict with SAMBA 2.0.6. and it will not allow me to install the latest version of SAMBA. It gives me error messages while I am trying to install samba2.0.7 "Conflicts

looks like you sent this to the wrong person... ----- Forwarded message from JON GERDES <GERDESJ@gkn-whl.co.uk> ----- Envelope-to: mikef@mikef-linux-x86.matchmail.com Delivery-date: Thu, 15 Mar 2001 00:18:43 -0800 Date: Thu, 15 Mar 2001 08:17:40 +0000 From: "JON GERDES" <GERDESJ@gkn-whl.co.uk> To: <mfedyk@matchmail.com> Subject: Re: win98-samba2.0.7 = Network

I found something interesting that I think may apply here. Check this out... https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave *I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a very old APC BK650M which is controlled and sends its status via a special serial cable to the

Sorry, I guess it is */usr/syno/bin/synoups* On Fri, Aug 14, 2020 at 2:27 PM Todd Benivegna <todd at benivegna.com> wrote: > I found something interesting that I think may apply here. Check this > out... > > > > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave > > *I have the latest version of the Windows port of NUT (A UPS

Roger, I just ran a manual test, killing power and see what happens.  I set the Synology “Time before DiskStation goes into Safe mode” to 5 minutes so I didn’t have to wait like an hour until it powered down.  Here is the log: https://hastebin.com/ovuwilufeb.sql Everything appeared to be normal; the servers powered off and the Synology went into safe mode.  Power was then cut to the Synology

This is the essence of the last message from Synology: For Synology the problem is no problem... They simply say now, we never claimed we are compatible with Samba AD, only with Windows AD, Azure AD and Synology Directory Server: ?? ?"Domain/LDAP ?? ?Features ??? Seamless integration with Windows AD, Azure AD Domain Service, and LDAP servers" See:

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

On Wed, 7 Jun 2017, Robbie van der Walle wrote: > I am running NUT on a Synology NAS with attached a USB APC UPS. > Do you have upsd and upsmon running as daemons on the Synology DSM? > Yes I have them both running on the Synology DSM:? > root? ? ? 7236 ? ? 1? 0 Jun01 ?? ? ? ? 00:00:16 /usr/sbin/upsd > root? ? ? 7741 ? ? 1? 0 Jun01 ?? ? ? ? 00:00:00

There was a Travis Wenks here, who has/had the same problems. I'm still hoping, he's reading the Samba mail list and tell me if he has still the same problems and we maybe can ally for this. Maybe the maintainers who has answered to the bug report can give some advice, too. The problem for me is that the developers from Synology think it can't be their fault. It's a little

On 8/1/20 11:25 PM, Todd Benivegna wrote: > I'm hoping that someone can shed some light on this… I have a Synology > NAS (DS416) that has a feature where you can enable a “Network UPS > Server” which is a NUT server.  I have been trying to get the Synology > to shut down three Ubuntu 20.04 servers that I have. While it does > work when I test it out manually, sometimes when

On 20/06/2023 14:11, Ingo Asche via samba wrote: > Hi All, > > the Synology support is claiming this bug is the reason for the access > problems via hostname (Kerberos): > https://bugzilla.samba.org/show_bug.cgi?id=14213 > > These log entries in log.wb-ADNAME are given as evidence: > > ../../source3/winbindd/winbindd_msrpc.c:307: [2023/06/14 > 22:13:42.913399,

Larry, I have not edited a single file, including anything to do with NUT, on the Synology via ssh.... ever. How is yours configured in the UI? Do you have it set to go into safe mode after a certain number minutes? Earlier, I was just copying and pasting the contents of some files to Roger but did not change anything. -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 8:16 AM -0400,

Synology ( https://www.synology.com/en-global ) is one of best selling brands of consumer/prosumer/SMB NASes, with revenue estimated to be in the $100M+ range. Several of their NAS backup options use rsync either explicitly or under the hood (NAS-to-Remote-NAS backup, Shared-Folder-Sync), and they run the rsync daemon (under File Services). rsync is an integral part of their solution. They use a

> Since it's NUT in the NAS which is deciding to order the shutdown, it would be > useful to see upsmon.conf, upssched.conf and upssched-cmd (or whatever Synology > use if anything) from the NAS to see what criteria they use. upsmon.conf (on Synology): RUN_AS_USER root MONITOR ups at localhost 1 monuser secret master MINSUPPLIES 1 SHUTDOWNCMD "" NOTIFYCMD /usr/sbin/upssched