Can't connect to internal address anymore

Post your questions about myQNAPcloud service here.
Post Reply
philpham
New here
Posts: 4
Joined: Wed Mar 25, 2009 9:55 pm

Can't connect to internal address anymore

Post by philpham » Sun Nov 10, 2019 12:20 am

I'm stumped.

I installed the myQNAPcloud service and rebooted my TVS-682. Once it came back online I couldn't connect to the internal 10.0.5.x address anymore. However I can launch myQNAPCloud and connect to the external remote address still.

I can see the device locally via a port scanner. But I can't ping it, I can't connect to the web admin console, I can't connect to it via my file browser. etc.

Any ideas?

dolbyman
Guru
Posts: 15478
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Can't connect to internal address anymore

Post by dolbyman » Sun Nov 10, 2019 1:11 am

qnap cloud only enables portforwards(upnp) and sets up a ddns..unless you enabled white or blacklists, it shouldn't lock you out on your internal net

so the dhcp range of your router is set to 10.0.5.x?

also rethink qnap cloud...lots of nas getting hacked by exposing them

Post Reply

Return to “myQNAPcloud service”