similar to: Windows XP clients

Hi, I have an Eaton 5SC UPS with only 1 USB communication port, but... I need 3 devices to safely switch off in case of power failure, 2 Synology NAS and 1 PC under Windows 7 (soon 10)! So I've decided to connect the UPS to the main NAS (via the USB cable), enabled the "Network UPS server" on the NAS, entered the other NAS and PC IP addresses to let them receive NUT messages in case

Hi, Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work

On Fri, 7 Sep 2018, Ong, Kevin wrote: > Any comments here? I am not a WinNUT user, but in general NUT clients do not produce their own log files. If you want more detail, you have to set the debug options and then look in your system logs. Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave ... POWERDOWNFLAG /usr/local/ups/etc/killpower My

Version 2.0.4 on CentOS (RHEL 4) I goofed on my original post and sent it to the bounce. Between then and now I have done some further digging and found the real issue. I was having an issue with the ups.conf file not being read after the 21st entry. Turns out this was were the first error occurred. I could move the entries around in the file and get them to load. What I did not realize is where

Version 2.0.4 on CentOS (RHEL 4) I goofed on my original post and sent it to the bounce. Between then and now I have done some further digging and found the real issue. I was having an issue with the ups.conf file not being read after the 21st entry. Turns out this was were the first error occurred. I could move the entries around in the file and get them to load. What I did not realize is where

I changed IP to NAS IP instead of my PC IP and also used NAS login and pass. Didn't work. When I wanted to launch WinNUT with new settings I got: "Fatal error: insufficient power configured!" (same as before) I got this log: Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 Level INFO

Hi Charles, Are there any logs generated by the WinNUT client? I'm trying to configure it for the first time and I cannot make it to work. Here are my settings: Nut.conf MODE=netclient Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave MINSUPPLIES 1 SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME

I am aware of 2 windows nut clients both interestingly called winnut. One (winnut 2.0.0b) is a service based client based on a port of the but client code (I think). The other is a GUI client based on (I think again) on knutclient . I have corresponded with both authors about a feature request - to allow the shut-down action to be (optionally) a windows hibernate. This seems a very

Hi All! This time I'm using Nut 2.2.0, Debian etch and kernel v. 2.6.23.9. My hardware config is quite simple. There are 2 PCs connected to my PowerMust 600VA. One is mensioned above the other is a Windows PC using Winnut 2.0.0b. The Linux PC is connected to the UPS via a serial cable and acts as the server. The problem is that both upsmon and winnut disconnect regularly but in random

All, I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061. I then attempted to connect my desktop via SNMP. My desktop is running Arch Linux, with a

Thanks, the strange is that I could set in this way the master user. At NAS4Free forum cannot get help, I presented the problem there too, but no real help. On Thu, Aug 22, 2013 at 2:19 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > > > Having the next problem, manually adding via WinSCP in the upsd.users > file the

On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > Thanks, the strange is that I could set in this way the master user. That is odd. The development version of NAS4Free seems to be regenerating the entire upsd.users file: http://sourceforge.net/p/nas4free/code/848/tree/trunk/build/ports/nut/files/nut.sh.in To address your original concern (adding remote users for monitoring), I would

Hello Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. NAS4Free is version 9.1.0.1 rev 724 and NUT is the version what is included.

I'm running Fedora14 on all machines, including my wife's -- and I'm the nearest (distant) thing there is to tech support. She's far more likely to outlive me than I her; so I want to install something requiring a lot less maintenance on her machine, so that she'll have it and be used to it, years ahead of need. I'm thinking CentOS 6, whenever it's ready, is

Hello All links I can find for winnut are not responding.. Anyone got a working link or maybe can send the package to me privately? /Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060410/717c77a2/attachment.html

Dear List, I am a bit uncertain about some aspects of NUT and have not been able to find the desired info in the documentation. We have a server monitoring the network and it is also running the ups/nut-daemon. Together with some other important servers (all Linux) it is logical to make these monitor the UPS as 'master'. While other servers (mostly windows running winnut, some linux)

[attachments trimmed] Begin forwarded message: > From: eric kreuwels > Subject: UPSC based Windows Client > Date: October 13, 2013 4:43:31 PM EDT > To: nut-upsdev at lists.alioth.debian.org > > > Dear developers > > Last month I wrote WinUPSC, a Windows task tray UPS monitor. WinUPSC re-uses the UPSC logic to poll the UPS. > This initial version was tested

Thank You very much !!! Now I see how was entered the master password in the file : "-v "concat(' password = ',//system/password)" -n \" I will test the proposed solution. Two questions - Do I need separate users for each WinNUT client or they can use the same user for monitoring&shutdown client machines ? - This is maybe a newbie question,

I want to try to use NUT on Linux server, but most of the servers I need to shutdown are Windows. Before I try to install I wanted to ask you how stable is the Windows Beta of NUT ? I need only the client part of the Windows port, only to shut down the Windows servers -------------- next part -------------- An HTML attachment was scrubbed... URL:

[Please remember to copy the list.] On Oct 15, 2013, at 8:45 AM, eric kreuwels wrote: > Hi Charles > > Thanks for your answer. Good questions/suggestions. I copied both the WinUPSC and the installer project on my GDRIVE and shared it with you: > https://docs.google.com/file/d/0B0mSjYYj84-6ZGM4MWZfMnFxbUU/edit?usp=sharing > > Archiving WinUPSC in the NUT GitHub would be my