jtp10181
Senior Member
Router: AC56R
Firmware: 378.52 (plan to upgrade to _2 tomorrow)
I noticed today that I was having issues access my webserver from inside the network using the DDNS hostname. I remembered seeing NAT Loopback so I google searched it and sure enough that seemed to be exactly the problem (it wasnt working). The setting was set to "Merlin" so I changed it to "ASUS". Poof it worked fine now.
I was also having an issue where if I went to my http://DDNS (default port 80) from OUTSIDE or INSIDE my network I would get the router interface page. I thought this was odd since the outside facing one is set to a different port. Now with that NAT Loopback setting changed, this also seems to be resolved. Yes I do want WAN access to the interface so I can check on the network when I am traveling. Might setup a VPN eventually but this works for now.
Firmware: 378.52 (plan to upgrade to _2 tomorrow)
I noticed today that I was having issues access my webserver from inside the network using the DDNS hostname. I remembered seeing NAT Loopback so I google searched it and sure enough that seemed to be exactly the problem (it wasnt working). The setting was set to "Merlin" so I changed it to "ASUS". Poof it worked fine now.
I was also having an issue where if I went to my http://DDNS (default port 80) from OUTSIDE or INSIDE my network I would get the router interface page. I thought this was odd since the outside facing one is set to a different port. Now with that NAT Loopback setting changed, this also seems to be resolved. Yes I do want WAN access to the interface so I can check on the network when I am traveling. Might setup a VPN eventually but this works for now.