Router G3100 Port and port forwarding

On my previous Tplink router setuo, I was using port forwarding to access individual surveillance cameras, remotely, while traveling. I am getting ready to setup that to see if I can really continue to use G3100.

Are others using port forwarding successfully on this G3100 router? I would appreciate any insights into this.

Accepted answers

dslr595148

@newbieuser wrote:
I am having the same issue. I can do port forwarding for RDP. It use to work before I upgraded to the G3100.

I have tried everything.

I have tested the port and its open but still cant RDP. I can do it inside the network but outside I cant. I use IP and my DDNS and still no luck.

I done it this way but still does not work..Keep in mind I used port 3389 not the one in the example. I got the photo from the internet. But its the same configuration but using port 3389 for both UDP and TCP.

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

https://www.yougetsignal.com/tools/open-ports/

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.

If you use an inbound client side port checker like http://www.pcwintech.com/simple-port-tester or from https://portforward.com/help/portcheck.htm then be sure that:

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.

#3 Once you know that the port is open from the outside (not talking about from behind the router), it will be explained what is going on.

All comments

Capricorn1

I don't have this router myself, but it's got a pretty big G3100 User Manual as a PDF you can download. Port forwarding starts on page 93. It looks reasonably similar to how the G1100 worked.

newbieuser1

I am having the same issue. I can do port forwarding for RDP. It use to work before I upgraded to the G3100.

I have tried everything.

I have tested the port and its open but still cant RDP. I can do it inside the network but outside I cant. I use IP and my DDNS and still no luck.

I done it this way but still does not work..Keep in mind I used port 3389 not the one in the example. I got the photo from the internet. But its the same configuration but using port 3389 for both UDP and TCP.

I even did it for 3389 --> 3389 instead of TCP any and UDP any

dslr595148

@newbieuser wrote:
I am having the same issue. I can do port forwarding for RDP. It use to work before I upgraded to the G3100.

I have tried everything.

I have tested the port and its open but still cant RDP. I can do it inside the network but outside I cant. I use IP and my DDNS and still no luck.

I done it this way but still does not work..Keep in mind I used port 3389 not the one in the example. I got the photo from the internet. But its the same configuration but using port 3389 for both UDP and TCP.

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

https://www.yougetsignal.com/tools/open-ports/

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.

If you use an inbound client side port checker like http://www.pcwintech.com/simple-port-tester or from https://portforward.com/help/portcheck.htm then be sure that:

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.

#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.

#3 Once you know that the port is open from the outside (not talking about from behind the router), it will be explained what is going on.

bkahn1

I am having the same problem and tried checking to see if the port is open. It does not appear to be open when I check from my phone connected to LTE - so outside of my network.

I am trying to forward HTTPS (443) to an internal server. This worked with my previous router but not the G3100.

idiot_wind

Hello,

I believe that I am having the same issue.

- I can use RDP on the local 192 LAN with no issues.

- I can get to the DynDNS hostname externally to login into the router.

- When using port checker on the PC that I am trying to connect to I see

0 - Port 3389 is closed on IP ADDRESS OF THE ROUTER when port forwarding is disabled

0- Port 3389 is open on IP ADDRESS OF THE ROUTER when port forwarding is enabled.

Any additional direction would be greatly appreciated.

Best regards,

frank

Eman1340

can't access my camera system via internet after getting new router it only works on WiFi but not outside tried all that port forwarding stuff and still can't fix it ( I'm a computer illiterate) Help

thx

Delete Message

PedalLove

I have a G3100 ( HW: 1103, FW: 1.3.6.27) and have not been able to get port forwarding to work. Can anyone confirm that it does in fact work on this model and firmware? I've heard that there are some versions where it doesn't work at all. I'd like to know if my problems are caused by my settings or if the router has a problem.

Thanks.

PedalLove

I solved my own issue and got port forwarding to work. I had to delete the entry in Port Forwarding Rules that I had set up for the port I needed and instead, specifically identify the ports in the Firewall - Port Forwarding section. It seems like creating a port forwarding rule for my application and applying it in the firewall doesn't work. In the Firewall section, I simply had to use the "Custom Ports" option instead of the application rule that I had created previously. Now it works!

idiot_wind

Great!! Nice work!! Thanks for sharing, when I have a couple of minutes and the ability to test I will try your solution. Thanks again for sharing!!!

TJ771

1) Goto Firewall -> Port Forwarding

2) Enter IP address from the Select IP from Menu

3) Under Application to Forward, enter the custom IP address

4) Click the "Add>" on the next line. Do *not* click the Apply at the bottom of the page.

The "Apply" button is for updating any change in Applied Rules.

SalG53

SOLVED!!!

Left Menu: Firewall

Top Menu: Port Forwarding

Select Advanced in center of options

Select IP From Left Dropdown

Select: Custom Ports from Right Dropdown

Protocol = TCP

Source Ports = ANY

Destination Ports = Select Specify & (enter the port)

Select Add

Complete 🙂

Check that the port is open on : https://www.yougetsignal.com/tools/open-ports/

GlockMan34

How to add Port Forwarding Group of ports/protocols to your firewall:

First create a Port Forward Rule, go to Advanced/Security & Firewall/Port Forwarding Rule. Create a rule and add all the protocols/ports needed (e.g. L2TP) and save it. You'd think you could go to "Port Forwarding" and add it now but it doesn't show in the drop down list. Navigate to Advanced/Network Settings/Static NAT, create a rule adding your device, your public IP, select the check box "Enable Port Forwarding" then select the "Port Forwarding Rule" you created. It'll be on the drop down list. Apply your changes, navigate to Port Forwarding and you'll see a new Group rule was added. This worked perfectly for me to enable L2TP and all the protocols & ports it requires. I've attached some screen pics to help. Hope this helps, it was a pain to figure out.

[Deleted User]

As this thread is now over two years old, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.