How to setup WinNUT Client on Win 10 with synology

[witzker]

I put in the NUT Host IP
As port for Synology 3493
Smart-UPS C 1500 as shown in Synology Host

username and PW for Synology Admin

When I click connect nothing happens.
Pls Help

[gbakeman]

When I was setting up the original NUT software to talk to a Synology host, I found out that Synology uses a hardcoded username/password to connect to their NUT software. In /etc/syno/etc/ups/ups.users, the username is monuser and password is secret. Although when I just tried this with WinNUT, it did not indicate a successful or failed connection, so I think it may be silently failing somewhere.

[FileCity]

I always setup my NUT server (with the UPS connected to it) on a Linux machine and then I setup each clients.
You can use a Raspberry Pi as server, works very well and it's using the complete NUT package with all options available.

[gbakeman]

Update for @witzker: I was able to get this working with my Synology device.

On your Diskstation web page, go to Control Panel, Hardware & Power, then click on the UPS tab. Make sure Enable UPS server is checked, then click the Permitted DiskStation devices button. Type in the IP address for your computer running WinNUT. You might need to put in both IPv4 and IPv6 addresses, I'm not clear on which one is preferred. After you've done that, click OK and then Apply. Now open the Options for WinNUT. Type in the hostname or IP for your diskstation in NUT host. Port can be left at 3493, and UPS Name left at UPSName. For login, type upsmon, and for password, type secret. Click OK, and it should connect.

Please let us know if you have any issues with this.

[gawindx]

@tgp1994
Can you take some screenshots and post them? I will have to do a wiki one day or another and that will allow me to inform specific cases.

[gbakeman]

Sure! Here's the first part:

1. Navigate to DiskStation's webui
2. Open Control Panel
3. Find the Hardware & Power section
4. Open the UPS tab
5. Make sure Enable network UPS server is checked, then click Permitted DistStation Devices
6. Put in the WinNUT's client IP address, and click OK
7. Finally click Apply (important!)

Finaly step, in WinNUT:

1. Open WinNUT, and open the Settings menu.
2. Put in the hostname or IP address of your DiskStation.
3. Set login and password as I've set
4. Click OK, and it should connect.

[SeeBer61]

I've just recently set up my UPS (APC Back-UPS Pro) to secure my Diskstations. I've set up UPS monitoring with automated shutdown (to safe mode) in my DS220+ as a server and DS213+ as a client. Now I was looking for a way to include my PCs into this and found this project. Great - love it !!

Actually it took my only one hour to set everything up including configuring Windows NUT client. After some trial & error I did some research and found that only

ups works as a parameter for the UPS Name
3493 as NUT Port, upsmon as Login and secret as password are still the default values in DSM6.x

[gbakeman]

You're right - I don't know why I didn't figure it out before, but I had the ups name wrong the whole time until recently. I'll need to redo the screenshots...

[gfairchild]

I'm trying to get WinNUT 2.0.7722.30975 working with my Synology DS1019+, and I'm having issues getting WinNUT to talk to the NAS. I'm hoping some of you guys might be able to help.

As you can see here, I've got the UPS attached to the NAS:

I've got my PC's IP included in the list of permitted devices:

I've verified my PC's local IP both in my router's device list table, as well as in my Windows networking settings.

I've plugged everything in WinNUT as best I can:

Here, I've tried both monuser and upsmon as the login, and secret is the password. Additionally, I've verified the IP of my NAS, and I've also tried the NAS' hostname.

When I try to list UPS variables, I get this error:

[Id 7: 2/22/2021 9:26:54 PM] Connection to Nut Host 192.168.1.46:3493 Failed: Connection to Nut Host seem broken when Retrieving ListUPSVars

Does anyone have any ideas? The firewall on the NAS is completely disabled, so it shouldn't be that. Any help is appreciated!

[gawindx]

Try With « Polling interval » >=1 in your options.

[gfairchild]

Try With « Polling interval » >=1 in your options.

Ok, that's hilarious; that worked immediately! I should've tried tweaking that setting! Thank you!

[gfairchild]

One more minor question: I thought I could put a hostname in the NUT host field, but it doesn't seem to work. If I specify the IP of my NAS, I can connect no problem, but if I put the hostname, I get this error:

[Id 8: 2/23/2021 12:04:23 PM] Connection to Nut Host <hostname>:3493 Failed: Access is denied.

Is this expected behavior?

[gbakeman]

Just want to chime in here: I was having issues connecting to my Synology just like you, and the reason seemed to be because I was using an IPv4/v6 combined LAN and the allowed hosts list is very strict about what address you put in. So if I put the hostname in, it resolves to the IPv6 address when I had only put my v4 address in the allowed hosts list.

To work around this, you'll want to make sure you have both IPv4 and v6 addresses in the allowed hosts list, or enter the IPv4 address when you connect. As a note to us developing WinNUT, perhaps we can attempt connection over both addresses if we detect a Synology host or get access denied the first time?

[gawindx]

Well seen for the IPV4 / 6 combo.

@gbakeman, For your suggestion, it would have to be studied but on this blow I could not certainly not develop it alone, I will need one or more beta testers who have a synology.

It will be seen for v2.1 when it starts to be sufficiently developed.

[gfairchild]

Just want to chime in here: I was having issues connecting to my Synology just like you, and the reason seemed to be because I was using an IPv4/v6 combined LAN and the allowed hosts list is very strict about what address you put in. So if I put the hostname in, it resolves to the IPv6 address when I had only put my v4 address in the allowed hosts list.

To work around this, you'll want to make sure you have both IPv4 and v6 addresses in the allowed hosts list, or enter the IPv4 address when you connect. As a note to us developing WinNUT, perhaps we can attempt connection over both addresses if we detect a Synology host or get access denied the first time?

Nice to note. I just put my local IPv6 address in the list of permitted devices:

But this still doesn't seem to enable me to connect using the NAS' hostname. WinNUT still yields this error:

[Id 27: 2/23/2021 1:50:36 PM] Connection to Nut Host <hostname>:3493 Failed: Access is denied.

It still only works if I provide the IPv4 address. I tried providing the NAS' IPv6 address in the NUT host field, but that's not working either.

@gawindx, I'm happy to help test.