Hi, I have TS-453 which decided this morning to “stop working”, i.e. not responding to any of the 2 network interfaces connected to the local network. The system is on the latest published firmware, updated perhaps week ago and the apps were updated to the latest versions at the same time.
I rebooted the network and the NAS, and on its screen everything seems fine, it boots up, checks volumes, mounts volumes - no errors, all green LEDs, both network interfaces show they are working ok. But… when I try pinging any of the IPs assigned to it or accessing the web interface, it just does not respond. I checked my very-flat home LAN and there is nothing suddenly preventing traffic to the NAS either.
What caught my attention was that during the NAS start-up, at one point the NAS becomes pingable on both network cards. Then it finishes the boot sequence, sounds the usual long beep to signal boot completion and then shortly afterwards the network communication is stopped. I tried access from 3 different devices which should rule out that a single device misbehaved somehow and QNAP firewall blocked it (although I am not sure if QNAP Firewall would detect/block DOS attacks anyways).
My suspicion is that either:
a) the network stack on the NAS is stopped or corrupted or
b) perhaps the QNAP Firewall App that is installed decides to block the rest of the local network.
I think (b) is probably more likely as for (a) I would expect network config or stack to be corrupted if there was an update (perhaps QNAP security updates that go in automatically/unattended?). At least (b) seems easier to check before going nuclear.
Is there a way to unblock/check/reset QNAP Firewall App rules (if that is the case), or check the status/health of the network stack within the QNAP OS?
For example, would any firewall rules clear out after a set period of time, e.g. if firewall thought it was under DOS attack, would it block IPs for e.g. 24 hours so I could just try again in a day?
Thank you for any help or suggestions