NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6250 does not persist ddns
A free ddns account has been created at NoIP, port forwarding configured at the router and the NoIP account credentials and dns name entered in Advanced Setup, Dynamin DNS. The firewall has been conf...
Doumo arigatou gozaimasu
Especially for all of your valuable time. I believe the issue is just now resolved. The problem was using my wireless adapter as a bridge to a virtual machine. It took me a couple of days to think of stringing a long cable to the router to see what might happen. When I looked at adapter properties I saw that the wireless was offline. No wonder the port was down. Lesson learned. Hardwire from now on.
I assume that offering to forward incoming port 80 means that the router is capable of doing such. After all, it has demonstrated that it can. So I'd like to know why you are not convinced it can be used that way.
What I did not describe was that the IP address to which traffic is forwarded is a bridge to a virtual machine. That's the reason for mentioning the firewall - it's conceivable that it could block traffic to the VM. Altho' my test of that was that adding the rule made no difference in performance.
It remains unclear whether the router or No-IP is causing the time out. It is clear to me, at least, that clicking on the apply button does enable traffic to pass if just prior to the click the connection times out.
Because I know that other more advanced router models (like the R9000) block 443/TCP for port forwarding as long as it's in use for the LAN side management - even if a different https port is active on the WAN/Internet. And yes, 443/TCP is offered for port forwarding, too. Even UPnP PMP requests appear to be handled, kind of.
So confirm the firewall you talk of is part of the VM platform or of the VM - but not on the R6250?
geoBrooks wrote:It remains unclear whether the router or No-IP is causing the time out. It is clear to me, at least, that clicking on the apply button does enable traffic to pass if just prior to the click the connection times out.
It's not No-IP ... the DDNS service will keep the name-to-IPv4 certainly longer than five minutes.
Beyond what you experience - that's the fishy part I have in mind. Test with a different, non-stanard port, e.g. 81/TCP to compare.
Firewall is Norton Security. Host is Windows 10 Pro1903, VM in Hyper-V.
My latest theory: there may be a possible conflict between the R6250's ddns updating and the No-IP updating service. I just learned that the No-IP service is not required if the router says it can do it.
I'm now experimenting with each service to see if anything can allow connecting after more than five minutes.
geoBrooks wrote:My latest theory: there may be a possible conflict between the R6250's ddns updating and the No-IP updating service. I just learned that the No-IP service is not required if the router says it can do it.
Don't run theories - the router won't update any DDNS service unless the IP address does change, or the service requires a refresh - look up the DDNS name by dig or nslookup or whatever utility and compare its returned A record - the IPv4 address the client would connect to. No rocket science.
Last but not least, are you testing from the same local [W]LAN or from another independent Internet connection, too?
Testing from local. It appears to correlate wit No-IP's port check. Mistake?