![]() this is just basic troubleshoot when something doesn't work as it should. If it doesn't work at this point, then i'm out of ideas. Then you login to the qnap qts using default password (make sure to change this). then you may need to soft reset the qnap (1 beep only). If it still doesn't, you could try rebooting your QNAP, router and pc. Then go back qfinder and open file in explorer again. Go to windows 10 network status > change adapter options. ![]() Tip: The performance profile in Step 9 refers to how the LUN. ![]() Be mindful of capslock if it's enabled at the time.Īfter adding, use qfinder and click open file in explorer. However, this setup does not provide any redundancy. try remove it then re-add (and type your credentials carefully). Identify the NAS you want to connect to from the list. Tip: If you cannot find the NAS, make sure that it is on the same network as your computer. Then check in windows credentials whether there is an entry for your NAS. Qfinder Pro automatically searches and displays all QNAP NAS on the same network. In windows 10, type in the start bar "credential manager". Instead of mapping, i use explorer shortcuts, which is basically qfinder > explore (or you can type out the url in the windows explorer bar which is tedious) To map a network drive for the QNAP, you use qfinder to do so. Disk: Host: Disk 1, Data creation date: -00-29.Firstly, did you setup a fix lan ip for your QNAP in your router? if you did then continue down the list to troubleshoot.ĭid you update windows 10? are you using latest stable QTS? did you reboot your pc and qnap to see if that fixed anything? Disk: Host: Disk 2, Data creation date: -00-29. It was a very similar event a year ago - but a simple reboot solved the problem. Started automatically updating the application. Now, I cannot see the NAS in Qfinder (after the 3-sec and then the 10-sec resets it was displayed for a few seconds but after refreshing it disappeared again). "Adapter 1" connected to the internet after checking NCSI. Set "Adapter 1" as system default gateway. ![]() The system was not shutdown properly last time. Set "Adapter 1" as the system default gateway. I bolded the two rows that are of interest where NAS2 became unresponsive (sometime on March 24 between 19:00 and 23:59) and when it was power cycled (March 26 around 20:15). I looked at the logs and it doesn't appear to be of much help. Logs are under QuLog Center, you could setup some alerts that may help diagnose. I'm thinking it could be the TS-231+ unit itself that's defective, or maybe the HDDs but hoping I can find info that would give me a better picture of what's happening. Is there anything I can do or logs I can consult to determine why NAS2 becomes unresponsive? It's strange that NAS1 is rock solid and never has any issues, while NAS2 is consistently locking up each month, but at random times. NAS2 uses identical WD RED drives and is connected to a UPS to mitigate power failures. I usually install the latest firmware within a few weeks of being released. Other times, it remains unresponsive for hours/days and the only way to get it working again is to power cycle the NAS. Once NAS2 becomes unresponsive (which occurs once or twice a month), it sometimes "fixes" itself after 15-20 minutes and everything becomes accessible again. I am however still able to ping NAS2 when this happens. no longer showing up in the QNAP QFinder Pro app.not being able to login via the web interface (page times out).mapped network drives not being accessible.NAS1 works perfectly but NAS2 randomly becomes unresponsive which results in the following: I have two TS-231+ on the same network which I'll call NAS1 and NAS2 for clarity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |