Hello to everyone, I’ve a TS-251D, and a few days ago I updated the firmware to the following release : 5.2.8.3332.
I didn’t notice any errors during the update, and then I leave the office till today, where I notice that the NAS was not reacheble from my PC. I checked all the usual errors (network cable, firewall, antivirus) but all was exactly as I leave the NAS after the update.
The strange things is that if I unplug the cable for few second, and I connect again the same cable, Qfinder Pro, find the device, but any action after that give an error because is like the NAS was disconnected, in fact if I run again the search, it didn’t find the NAS, until I unplug again the network cable.
I changed different network cable, but the resul was the same.
Question:
is it possible to connect the NAS without network?
Is it possible to do a factory reset without lost the data in the driver?
The IP address is correct (PC - 192.168.XXX.AAA; NAS - 192.168.XXX.BBB) while the Subnet I know the PC one, but I don’t know the NAS one, because I don’t have access.
I tried to connect directly the network cable to the PC, as explained in the report linked, but the Qfindpro it doesn’t find any
OK. So you can do a 3 second reset and that should reset the admin password and your network settings. The NAS will then get an IP address from your DHCP server and then it should show up in Qfinder.
Hi NA9D, I’ve an update; I tried to connect the NAS through the internet (MYQNAPCloud) and is reachable and usable (I download a file)so the network card works correctly; I suppose the problem is the PC, now I’ll try to install Qfinder pro on another PC and make some tests with it.
FIXED! Yes, it was the NAS Firewall that blocked all the inbound connections. Thanks for the desktop connection through MyQNAPcloud, I was able to update the firewall app, and find that all the connections from my network were blocked (I don’t know why). I need to put more attention when I update/change the configuration.
Many thanks to NA9D and dosborre for yours support
…you are right, it was my mistake; after the firmware update, I checked if everything was good, and I noticed the firewall was not active, so I activated it without thinking too much…
BTW, it was good to check all the rest and test the recovery plan (thanks all the other backups I put in place).