How To Find Port Forwarding On AT&T?


How To Find Port Forwarding On AT&T?

Overview

This article we will see port forwarding on AT&T Router,  applies to ALL existing AT&T DSL, U-Verse and the new GigaPower service. 

It will allow you to open your public IP port(s) for your private LAN clients that are behind a router or if you just want to give internet access to local machines on an AT&T connection.

The process is pretty straightforward once you know where to look; if you’re experiencing difficulty, this should help you along.

Note:

This Article will show how to find/setup Port Forwarding ONLY on a router (ATT U-verse or GigaPower). However, the principles apply to ALL routers and ALL service providers (including cable companies like Comcast or COX). This guide simply shows how it’s done with AT&T equipment and doesn’t go into advanced settings such as Virtual Servers, DMZs etc. This tutorial also does not show how to configure UPnP as there is no need – port forwarding can be used in conjunction with UPnP & your router may not support it.

Virtual Servers

Virtual Servers is a more advanced topic and simply adds another port to the list of rules so you can tell your service provider’s device to forward any traffic on both ports instead of just one. Don’t worry about this if you’re brand new to port forwarding as it literally takes half a minute once you know where the option is located.

How to Port Forwarding on AT&T Router

First we start by going into our account at ATT Uverse or Giga .

AT&T Control Panel >When you enter, click the Additional Online Options drop-down menu and select Home Control Online.

First, locate your gateway device in the row of devices directly under Provisioning & Device Management. Let’s assume that it is a Motorola NVG510 which uses a web interface found at http://192.168.1.254/ . Other models don’t have these default IP addresses but they’ll be on AT&T’s website if not simply do a Google search for “ATT [Device Name] Login”. 

For example, an NVG589 would simply search for “ATT NVG589 Login”. 

Once you’ve located your gateway IP address, open up your favorite web browser and enter the following: http://192.168.1.254.

Log in with the username root (this is case-sensitive) and switch it to admin using the password provided on AT&T’s website or by calling customer service if you don’t know what it is – do not use the one shown above because it’s just an example! Once logged into your router, click on Advanced at the top then Firewall Settings.

Enable/Select Port Forwarding option ,Enable both Port Forwarding and Port Triggering.

We now need to enable “Enable/Select Port Forwarding” which will open up the port. If you want to forward more than one port, simply checkmark additional ports and click Submit . Then select Apply at the bottom of the page so our changes take effect. Please note that AT&T does not recommend this nor can I assist in troubleshooting if you do it any other way than what is shown here – reading ahead may get you stuck trying things you don’t really need to do. There’s no reason why we can’t just do it this way and keep everything within reach for future changes or reference should we need it at a later date.

Steps After Port Forwarding is Enabled

Now that we’ve enabled Port Forwarding (and optionally Triggering), we need to tell the router which devices you want to forward those ports to. In my case, I’m going to forward external HTTP traffic on port 80 as well as internal HTTPS traffic on port 443 from anywhere to a single IP address – it’s really up to you if you have multiple devices behind your router or not and how many ports you need forwarded. For this example, let’s say 10.0.1.3 .

What we do now is enter a name for our rule under Name ✔ , enable Triggering ✔ , and put the IP Address of the device inside Allowed addresses ➡️ . Next select External Ports ✗ since we’re only allowing traffic from the public Internet (remember, this is a home router and we’re not plugging it into the back of our modem like you would in a business environment).

Finally, we now need to enter both external and internal ports for this rule. Since I’m forwarding traffic from the internet on port 80 (HTTP) as well as an internal device on port 443 (HTTPS), I will enter ports 80 & 443 respectively under External Port ✗ and Internal Port ✔ . If there were additional ports being forwarded or triggered, they could be entered here if so desired. Once done, click Submit at the bottom, wait a few seconds for it to confirm your changes, then Apply at the bottom once more to save your work.

Please note that having HTTP/2 enabled DOES NOT matter as I had originally thought. It appears to be a change in the way HTTP/2 functions and not related to port forwarding as initially assumed.

Conclusion

That’s it following the above procedure, Your ports should now be forwarded and active if connected correctly through your browser where you entered them or through any other software such as FileZilla with no issues.

If you entered the internal port incorrectly, you can always click Reset Rules at the bottom of this page and everything will go back to its defaults with the only difference being that Port Forwarding won’t be enabled anymore – then simply follow these steps again but this time put HTTPS (port 443) instead of HTTP (port 80) into Allowed addresses.

Recent Posts