I don't think the NAT Loopback issues claimed to have been solved in previous FW release 3.0.0.4.378.4376 is really fixed. On FW:3.0.0.4.378_4608 it works for a few minutes and it freezes indefinitely after that. If I reboot the router, it comes back for a few minutes again but it dies after that.
I have reset the router to factory defaults, upgraded it to the new release, reset it again to factory defaults and manually added couple of options that I use, namely MAC clone and PORT FORWARDING of port 80 to a web server. The rest is vanilla factory defaults.
I can access my web server from outside systems and cellular phones on GSM with no problems (i.e., port forwarding is working). I can also access it from inside the domain using the private 192.168.x.x IP address with no issues. But when I try to access it from inside the domain using the http://mydomainname.com/myservicename (i.e. using the NAT loopback) it works for the first few minutes but then it stops working all together and I get the message that service cannot be accessed. I have to reboot the router to get it to work again.
Has anyone else experienced this?
Can someone verify this?
Is there a way to open a ticket with ASUS?
This has been the case for both 378_4608 and 378_4376 versions.
Brad
I have reset the router to factory defaults, upgraded it to the new release, reset it again to factory defaults and manually added couple of options that I use, namely MAC clone and PORT FORWARDING of port 80 to a web server. The rest is vanilla factory defaults.
I can access my web server from outside systems and cellular phones on GSM with no problems (i.e., port forwarding is working). I can also access it from inside the domain using the private 192.168.x.x IP address with no issues. But when I try to access it from inside the domain using the http://mydomainname.com/myservicename (i.e. using the NAT loopback) it works for the first few minutes but then it stops working all together and I get the message that service cannot be accessed. I have to reboot the router to get it to work again.
Has anyone else experienced this?
Can someone verify this?
Is there a way to open a ticket with ASUS?
This has been the case for both 378_4608 and 378_4376 versions.
Brad