brightstar
New Around Here
Hi,
I'd a TP-Link Archer VR900 which had all sorts of lags and I've decided to upgrade to RT-AX88U.
The VR900 now acts as a bridge, and all other wired/wireless activity is done by the RT-AX88U. I have a local QNAP device which I previously logged in locally (xx.xx.xx.xx:yyyy) and now I can't.
The QNAP is connected through LAN over powerline adaptor and it's fully visible in the network client list. I've registered a DDNS with asuscomm, and when I'm outside my local network, I can access the device remotely using the DDNS, but I can't access it locally in my network, even when using the DDNS (previously I was able to with the VR900).
I've tried changing all sorts of AiProtection and such, but without any change.
What else should I be looking for?
P.S. 1 - Forgot to mention that I've manually assigned an IP address to the QNAP device, and there is a Virtual Server definition for the QNAP port and another port (diff. application within the QNAP).
P.S 2 - The router is flashed with the latest firmware 3.0.0.4.386_48631
Thanks!
I'd a TP-Link Archer VR900 which had all sorts of lags and I've decided to upgrade to RT-AX88U.
The VR900 now acts as a bridge, and all other wired/wireless activity is done by the RT-AX88U. I have a local QNAP device which I previously logged in locally (xx.xx.xx.xx:yyyy) and now I can't.
The QNAP is connected through LAN over powerline adaptor and it's fully visible in the network client list. I've registered a DDNS with asuscomm, and when I'm outside my local network, I can access the device remotely using the DDNS, but I can't access it locally in my network, even when using the DDNS (previously I was able to with the VR900).
I've tried changing all sorts of AiProtection and such, but without any change.
What else should I be looking for?
P.S. 1 - Forgot to mention that I've manually assigned an IP address to the QNAP device, and there is a Virtual Server definition for the QNAP port and another port (diff. application within the QNAP).
P.S 2 - The router is flashed with the latest firmware 3.0.0.4.386_48631
Thanks!
Last edited: