Remote Access Hangs

[RandomGeeza]

Not entirely sure if this is a Safari issue (since the most recent update), or whether the router is acting up. Although this problem happens on Chrome as well. Which implies it is the router.

I have access to my router setup as per. With a specified port for access. When I try to access the router outside my network on my static IP, the browser will not connect. It simply hangs and then reports no connection. I have not changed any settings... and am at a loss as to fixing it.

It used to work flawlessly. However, It works only when inside on my internal IP but not outside. Any suggestions. Thanks.

Edit: Another thing to add. My NAS which works on the same static IP, but obviously with a different port number works fine. So it also seems to suggest that it is a router issue?

[billion_fan]

No entirely sure if this is a Safari issue (since the most recent update), or whether the router is acting up. Although this problem happens on Chrome as well. Which implies it is the router.

I have access to my router setup as per. With a specified port for access. When I try to access the router outside my network on my static IP, the browser will not connect. It simply hangs and then reports no connection. I have not changed any settings... and am at a loss as to fixing it.

It used to work flawlessly. However, It works only when inside on my internal IP but not outside. Any suggestions. Thanks.

Edit: Another thing to add. My NAS which works on the same static IP, but obviously with a different port number works fine. So it also seems to suggest that it is a router issue?

Have you tried a reboot??

[RandomGeeza]

Yes... that was the first thing that I tried... WiIll try again to be sure.

[billion_fan]

Yes... that was the first thing that I tried... WiIll try again to be sure.

Can you PM me your WAN IP, so I can try from here.

Also try disabling and re-enabling the remote access feature.

[RandomGeeza]

Hi, I turned off and then back on the remote access instruction. And tried a second reboot.

It seems to have fixed it.

Odd behaviour, but working now. Thanks...