Why do I still need to sign in my QNAP ID when I am in LAN?
Applicable Products:
- The latest QNAP’ mobile APPs
Because the “old” connection info saved in an APP no longer works. By signing in the QNAP ID, our mobile APPs can then request the myQNAPcloud server to provide the latest connection info of the NAS.
This is how our APPs work:
Once an APP has been successfully logged in a NAS. The APP will save all the related connection information (such as system port number, LAN IP, WAN IP, myQNAPcloud device name and FQDN) and will keep unchanged until next log in.
Below are 2 common examples that help better understand how it works.
This is what usually happens:
Our APPs used to connect to the NAS without any issue. One day, there was an unexpected power shut down. The NAS got a new LAN IP assigned by the router. Thus, the older LAN IP no longer works to connect to the NAS. At this moment, when our APPs find that old info no longer works, it will ask the myQNAPcloud server what’s the latest information (here the new LAN IP address is needed) to connect to the NAS. By signing in the QNAP IDis requested if Access Control is not set to Public*, our APPs can then get the data from myQNAPcloud server.
This is also another common case:
You just enabled a firewall in your network environment and forgot to allow the phone to access the NAS in LAN. Since the phone is unable to connect to the NAS in LAN (blocked by firewall), our APPs will use myQNAPcloud Link (i.e. connecting the NAS remotely) to access the NAS instead of LAN IP. By connecting the NAS via myQNAPcloud Link, signing in the QNAP ID is requested if Access Control is not set to Public*.
This also applies to when you change the NAS system port number and forget to change the related connection setting in mobile APPs
*For more information about QNAP ID and access control; please refer to the link below. How to use myQNAPcloud (QID) to remotely manage a NAS?
