01-13-2020 05:44 AM - edited 01-13-2020 07:27 AM
I recently (last week) upgraded my old Actiontec router (MI424WR Rev 1) to the Quantum router, model Number G3100. Prior to the upgrade, I had port forwarding configured for RDP and several other applications. After the upgrade, and setting the same forwarding rules, I cannot RDP into any machines using my external IP address, but I can still access them using their internal addresses.
I've tried configuring multiple ports, directly connecting one of the machines to the Quantum router, disabling the firewall on the router entirely to allow all inbound connections, and nothing appears to work. There are no log entries in the router's firewall logs either, which I find somewhat suspect.
I have also tried disabling the machine's firewall (the one I want to RDP into) to rule it out as the cause. That had no effect, and the firewall logs (before I disabled it) do not show any DENY packets for inbound RDP connections, so I'm 99.99999% that it isn't the machine configuration. Plus, it works from internal connections.
I've also tried opening a different port, not RDP, and have the same results. I can access it (a simple TCP listener app) internally, but I cannot access it using my public IP address and mapped port (9999 in this case).
Here is a photo of the current configuration of the RDP mapping. This same configuration worked prior to the upgrade.
Solved! Go to Solution.
04-09-2020 10:38 AM
After entering your dynamic dns, go to DNS Server. Enter your dynamic dns (blah.duckdns.org) and your internal IP address for the device you want to reach. This does not solve the port forwarding issue, but actually works without having to forward any ports.
01-16-2020 05:28 AM - edited 01-16-2020 05:31 AM
See if the port is open from the outside.
#1 This could mean using a port checker.
An example of a web based port checker, is
If you use a web based port checker, be sure that:
the server is in the listening state and you are forwarding the ports that you want to check.
you are forwarding the ports that you want to check and the server that you are trying to forward is NOT in the listening state.
Stated reason that the server that you make sure the server trying to forward is NOT in the listening state when using an inbound client side port checker, when using this kind of port checker - it will try to listen on that port and you can not have two servers listening on the same port at the same time.
#2 Or you can have someone try to connect from the outside. When they do this, it does not have to be for RDP if desired - it just has to be server of sorts.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.
02-02-2020 10:40 PM
I have the same issue on the same device. It worked fine a few weeks ago and broke during the interim. You can hit the forwarding port on the G3100 and it responds but no traffic makes it to the destination device. My theory is something in a firmware update broke whatever IP forwarding they were doing. Their staff did not know when the current firmware update was applied nor how to roll back.
02-10-2020 06:26 PM
I am having the same issue trying to set up DuckDNS.org to Home Assistant, which should get me an SSL connection to my internal server if port forwarding worked properly. This all worked on the previous router.
02-24-2020 05:30 AM
Has anyone gotten a resolution to this problem ? I am employed in the Network/VOIP field and I set up port forwarding all the time on various equipment and something is definitely broken with this g3100 firmware. Just to add - setting my server static ip as dmz host, security to "low" adding port forwarding, port triggering, etc... and i still can not access it from the outside - I also confirmed that my "A" record for my domain is working, dns resolves ip so whether I use my public ip address or domain it just doesn't work
03-02-2020 08:36 AM
You need to go into the DNS Server screen and add an entry for the public DNS name mapped to the IP you're forwarding to. Don't ask me why but found on another forum and it worked. Bug in their software somewhere.
Friend just moved and the new place has a new Verizon G3100 router. So, I set up the forwarding ports to be the same as the old G1100 router. After troubleshooting, I gave up and talked with Verizon techs and found that the G3100 blocks connections going out and coming back in so you cannot test ports that you set up! That sucks but is manageable.
However, far worse, it means anything that you set up on your laptop or phone to get to "your place" will fail if you are actually at your place. Example: I have an app set up to view 8 cameras on site. I use DDNS to get there, which used to work no matter where I was, at home, on the road, etc. No longer, As soon as I'm in wifi reach of the G3100, it blocks my access!! So, I'm supposed to have 2 different apps set up to view cameras depending upon if I am near the G3100? Let's say you are Honeywell and have a G3100 in your office. You want to look at your wifi thermostat? You need a server in the cloud to access it because the G3100 (unlike any other router I know, the G1100, D-Link, etc) will block you from using a DDNS address (or your official Honeywell address) inside its realm.
Did I miss something? I suspect the G3100 wasn't all that tested or thought out - because in guessing that I might need to reboot to get port forwarding to work, the G3100 blocked all outgoing connections except from the router's diagnostic ping, after reboot! The tech had to reset the router to factory to get it to allow outgoing connections..??
OK, what did I miss? Time to rip out the G3100 and put the old G1100 in its place to get a proper working router?
03-03-2020 05:35 AM
This is a nice generic answer that totally ignores the issue, similar to asking if my router is turned on.
I do appreciate the other answers that confirm that this is a deficiency in a new firmware release, prior to us getting this new router, and there is a bizarre workaround by putting the IP of itself into the DNS?? Thus undermining the operation of the DDNS partially. Will try that in a bit.
Sorry, but generic answers that totally ignore the problem drive me crazy..
03-03-2020 06:05 AM
Hmm, if I understood, I enter blah.duckdns.org 173.xx.yy.zz, my external IP, into the DNS server and I can then access my stuff from inside the house. It didn't work for me. I have http https ftp a couple rdp's and a multi webcam server. I tried a couple after adding the entry. FYI, G3100 firmware is version 184.108.40.206.
Because she is paying Verizon for this G3100 and it is demented and the G1100 that she owns does work properly, unless there is a real coverage boost with the G3100 as Verizon claims, and I've only seen a couple more db, it's going back to Verizon.
Thanks for the reply and confirmation of the problem!
03-05-2020 03:40 PM
I have the exact problem. I open one HTTP/TCP port and I am unable to access it from my smartphone with http://MyDdnsHost:12345 - I get connection refused. Firewall log is enabled but none is showing any incoming requests.
Is anyone fixing this issue?