My takeaway here is to stick with IPv4 addresses in the Synology UI as well as WinNUT preferences. The fact that my NAS is only seeing the temporary IPv6 is concerning because if I'm supposed to rely on a whitelist in the Synology UI and that IPv6 address is changing with some regularity, then that'll mean that the whitelist is functionally useless. When I pasted that IPv6 address into the list of IPs that are permitted to access the NUT service, all of a sudden I can specify the NUT host in WinNUT to be either the IPv4, IPv6, or hostname of my NAS all 3 work equivalently now. So what Synology is seeing is my temporary IPv6 address, not the other one.
![synology ups server synology ups server](https://www.ewall.store/11044-large_default/synology-ds220-2gb-nas-server-ironwolf-20tb-2x10tb.jpg)
I thought to check my Synology logs to see what IP Synology's logs are capturing, and I see this: Of particular note is that temporary IPv6 address, which is different than the (non-temporary?) IPv6 address listed above it. Here's a screenshot of my network adapter properties:
#Synology ups server Pc
Lesson learned here: I guess you either need to figure out exactly which IPv6 address the application is using on your PC to establish the connection, add every IPv6 address assigned to your PC to the authorized clients list, disable IPv6 wholesale on your diskstation, or explicitly use IPv4 when connecting.Īh, your comment really helped! After digging around, for reasons I don't understand yet, I see the same thing. I added that to the list of authorized clients, and I can connect now. It ended up being a different address than I thought. I opened a connection with a terminal (KiTTY), then opened a network monitor (Process Hacker) and found the exact local endpoint it was using. I admit I still don't understand how IPv6 works, but for some reason my PC has multiple IPv6 addresses. I just double checked on my end, and I think I may have misremembered what I did! I was just now able to authenticate with an IPv6 connection. I tried providing the NAS' IPv6 address in the NUT host field, but that's not working I'm happy to help test. It still only works if I provide the IPv4 address. Connection to Nut Host :3493 Failed: Access is denied. I just put my local IPv6 address in the list of permitted devices:īut this still doesn't seem to enable me to connect using the NAS' hostname. 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? 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. 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. 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.