Ask a question
Thu, Oct 1, 2015 1:21 PM
5 years ago
We will be happy to help you with your router configuration. Are you looking to open a port on the U-verse gateway? If so, one thing that you can try first is setting the device in DMZ or passthrough mode to make sure everything will work correctly. Below are some instructions that go over it. It details how to do it with another router, but you can do it with any device. Just choose the gateway that matches yours.
Hope this helps.
AT&T Customer CareNeed help with an account specific question? Post a new question here on the forums by clicking the "Ask a Question" button.For additional support, please visit us at our AT&T services hub.Follow us on: Twitter @ATTHelp
4 years ago
I contacted AT&T ConnecTech Service rep. yesterday. The tech named "Daryl Fernandez" said UVerse customers must subscribe to an additional service which costs $15/ month in order to be able to gain access to cameras from outside the house. Here is the chat transcript:
We apologize about the issues and how they phrased their response. You do not have to pay for the access, but the paid subscription is to the support on getting it setup, since the cameras are not an AT&T product. Hopefully, setting up your cameras in DMZ mode helped. If not, please feel free to start a new thread stating what is happening, and the community has always been very helpful in trying to get things fixed.
3 years ago
2 years ago
ACE - Expert
Opening ports is not considered standard support. You do not have to pay for the ability, but you do have to pay if you want AT&T's help getting it set up.
AT&T just provides you a means to connect to the internet, its up to you to configure your home connection, or you can pay to get someone to do it for you.
https://portforward.com/ should have guides on how to do it though.
@rdomingue wrote:I have done the port forwarding and net/gaming configuration and it does not work so far.
Fixed that for you. Hundreds, if not thousands, of others have managed to make it work. If you want, post what you're trying to do and screenshots of what you did on the gateway and we'll give you feedback.
TRYING TO MAKE PORTS 85 AND 6036 ACCESSIBLE FROM OUTSIDE THE BOUNDARIES OF MY HOME NETWORK USING MY EXTERNAL IP ADDRESS.
I'VE DONE WHAT IS SHOWN IN THE ATTACHED SHARED FOLDER AND THAT'S ABOUT ALL THE INFORMATION I CAN FIND ON THE SUBJECT. I HAVE READ WHERE PEOPLE HAVE DONE THIS EXACT THING AND ITS WORK FOR THEM WITH OTHER AT&T SUPPLIED ROUTERS.
QUESTION: YOU KEEP MENTIONING MY CLAIMS OF HAVING A STATIC IP ADDRESS AS THOUGH IT IS NOT STATIC. WHAT ARE YOU GETTING AT? IS IT NOT TRULY A STATIC IP ADDRESS? IS THIS WHY IT IS NOT WORKING. PLEASE EXPOUND. ADDITIONALLY, DO YOU HAVE DOCUMENTATION ON WHAT IT TAKES TO MAKE THIS WORK SUCCESSFULLY WITH THE BGW210 ROUTER/MODEM? THANKS!
You have set up Port Forwarding and DMZplus to the same device. This is likely not going to work correctly. You want to do either one or the other in the AT&T gateway, not both.
Is 192.168.1.200 the actual device that has the ports open that you want to access from outside, or is it an intervening router?
If the former, port forwarding by itself should be good enough. If you wish, instead of doing port forwarding, you could effectively forward all ports by setting up DMZplus to the device, but if you do so, then you need to remove any port forwarding you set up.
If the latter, then you need to do DMZplus to 192.168.1.200, then do port forwarding inside 192.168.1.200 to the ultimate device. I don't think this is what you're doing.
A static address is one that doesn't change. You've been saying that you have a public static address. AT&T doesn't issue a single public static address. They issue a public dynamic address. It changes very rarely, and for most purposes you can treat it as static. However, when you mention you have a static address, then we're going to go off on static setup, not the standard setup.
Sorry, yes, DMZplus is the name used on some AT&T Gateways (the 2WIRE/PACE line), the other line uses the term IP Passthrough (models NVG*, BGW*). Same feature. It's similar to "bridge mode" in that:
1) The target device receives the public IP address from the gateway in response to a DHCP query
2) All traffic from the target device is passed to the Internet without changes (i.e. no NAT/PAT)
3) Unsolicited traffic from the Internet that passes any filters (there are default filters) and does't match a port forwarding or NAT translation is forwarded to the target device without NAT/PAT
At any time during your attempt to set this up have you done a factory reset? While I've never heard of it on the BGW specifically, many other gateways have had issues that have been corrected by doing a factory reset and clearing out the NVRAM (often this is because a new version of the firmware doesn't deal well with the config data in NVRAM). Sometimes it happens because the firmware just gets confused with data it wrote when it gets complicated.
There is no account specific information stored in your gateway that wouldn't be replaced automatically during the reload operation when it books back up afterwards.
How can we improve?
No tags available