03-26-2023 10:46 AM
Been using my QNAP NAS for several years now without trouble - directly connected to the ISP Router.
I recently got a Nest Wifi Pro setup, and had to move the NAS. It's now connected with cable to one of the Nest stations (not the primary one). However, I can no longer access the NAS.
- Google Home Wifi registers the NAS as being connected to the Mesh.
- NAS applications can see the NAS, but not SSH or log in to it with HTTP. Network drives can of course also not connect.
The Mesh is set up as it should be and everything else works as it should - it's only the NAS that isn't working. I'm sure I'm not the only one to have run into this problem before - anyone with a good idea of what might have gone wrong (and how to resolve it)? PCs and NAS look to be on the same subnet, so that doesn't seem like it should be the problem (generally speaking, it looks like it should work, but it doesn't).
Answered! Go to the Recommended Answer.
03-30-2023 03:01 PM
The solution to the problem I encountered here was a factory reset of the NAS (resetting all the NAS settings, but not the HDDs). Once that had been done (a looong time after it had been done - it took a long time to get back up), I was able to access the NAS again and log in using default passwords, etc.
Not sure what the real issue was, but I suspect the differences in the network between old setup and the new one must have caused some sort of issue.
03-26-2023 12:52 PM
Check the IP address. I'm willing to bet you were likely using a static IP for your NAS previously. The DHCP range for Nest is different that the standard one used by most routers.
03-26-2023 02:01 PM
Have never used static IP with this NAS and connection via HTTP has always been done via the IP address. That doesn't work anymore (I am of course connecting to the IP address identified by both the QFinder app as well as the Google Home app).
The only way I can currenly access the app is via the QManager app, but I suspect that is because it accesses it via the internet/QNAP cloud.
03-26-2023 04:48 PM
Is there some client isolation or subnetting going on with the Wifi Pro that it's not showing in the app interface? Currently, the setup is:
ISP[Bridge] (cable) -> Wifi Node[Router]
Wifi Node[Bridge] (cable) -> NAS
03-28-2023 11:25 AM - edited 03-28-2023 11:25 AM
Am assuming the suggestion here is to shut everything down and restart everything in the right order (and not only restart the router... not getting much use from the Nest Wifi units if they are off 😋).
Anyway - I've tried that, and tried it again now - and it unfortunately makes no difference.
03-30-2023 03:01 PM
The solution to the problem I encountered here was a factory reset of the NAS (resetting all the NAS settings, but not the HDDs). Once that had been done (a looong time after it had been done - it took a long time to get back up), I was able to access the NAS again and log in using default passwords, etc.
Not sure what the real issue was, but I suspect the differences in the network between old setup and the new one must have caused some sort of issue.
04-07-2023 09:11 AM
Hi folks,
@AfroPisces, @RachelGomez123, I appreciate your suggestions here.
@micax, I'm glad to hear that your NAS is already working with your Nest WiFi Pro! I wanted to check in to see if everything is sorted out on your end.
Feel free to inform me if you have additional questions or concerns.
Best,
Lovely
04-10-2023 10:33 PM
Hello everyone,
Chiming in to see if you still need assistance with this. Hope the previous post helped. Let us know if you have additional questions ― we'd love to help.
Thanks for lending a hand, @LovelyM.
Regards,
Abi
04-11-2023 11:36 PM
Hey folks,
I'm just checking in to make sure that you've seen our response. Please let us know if you have any other questions or concerns as I will be locking this in 24 hours.
Thanks,
Abi