Fiber Customers Having Trouble - Ports blocked?

Hey @RangerRik1,

We'd like to help you with the ports. Did you check the firewall configuration inside the computer as well? Are you using a third-party gateway? Where does the Traceroute begin getting request timeouts?      

Here is information on the ports that we block. Skip down to "What practices has AT&T adopted to manage network security?"

Here is more information on port forwarding, and ip passthrough if third party gateway is used.

Let us know if this helps.

Max, AT&T Community Specialist

I have the same problem with opening all ports but 80 they are all blocked and can not be opened despite spending 8 hours on the phone with att with tier 1,2 & 360 support. They now are sending it to line side support. Ports are being blocked before the service model/router model BGW210-700.

Have you checked the NAT table and added the ports to be opened. I have to do this for my security camera system. I added for TCP and UDP to open ports and this will let me view cams from outside of my home network ex. Cell phone. 

I had AT&T fiber installed at the beginning of April with 5 static IP addresses.  I have a SMTP server that was working well in both directions.  AT&T messed up my order and had to re-install/swap out router.  Now I can get inbound connections on tcp port 25 but when I send packets out on port 25 they never connect.  I have a network monitor between the router and my firewall and I see the packet going out but no connection is established.  When I rout port 25 through my Spectrum DHCP connection I can connect just fine.  I find it weird AT&T is blocking outbound SMTP connections.

Actually a lot of isps block out bound SMTP port 25. It's what all the mass mailing spam worms and hacking goes through. That'll be something for you to discuss with AT&T if you have a business account and static IP you can make an argument.  But I have a feeling they're going to block it. AT&T is the worst when it comes to this I actually had to convert a client over to spectrum for the sole reason of port forwarding and this ongoing issue. Best of luck to you...

The frustrating part is it has worked for ten years and it worked up until AT&T totally messed up my account.  I will try to open a ticket but I will need to let my blood pressure medicine kick in before I try

----UPDATE----

Opened up a support chat not expecting much but to start the expected multi-day process of escalating the ticket.  Was on chat for two minutes, agent said "try it now", and it worked.  Kudos to AT&T Fiber support.

I'm getting nowhere with AT&T.  They will NOT open the ports I need.  BGW320-505.  Firewall turned off, packet filter turned off, static IP's ordered and assigned to two different internal routers (with firewalls), DHCP off, IP Pass through off (and tried with it on, manual mode), NAT/Gaming off, Public subnet on, allow inbound traffic on.  I have opened the required ports on my internal routers.  Tests done with both portchecker.co and yougetsignal.com.  I can even hook up an Ubuntu computer with NO firewall directly up to the AT&T box...nothing in between, supposedly open to the world and I still can't get the ports opened.  

I've been on business tech support with 3 calls, over 4 hours.  I've factory reset the ATT box two times.  I've had their techs keep trying to reconfigure the AT&T box (the equivalent of "how you turned the box on?"...i.e., I've done everything they're trying to do multiple times already).  They even replaced my modem/router just to get identical results.  They refuse to pass me up to a network engineer.  A supervisor called me back and worked on it.  End result,  every time the response is, "it must be your equipment because our AT&T box is setup correctly".  I keep telling them, it is blocked on their side BEFORE it even hits the AT&T box.  It's like talking to a brick wall.  How can my striped, no firewall computer with a static IP that can easily surf the webs, that is hooked up directly to their ATT box not have open ports when theoretically ALL ports are open?  

I'm done...but based on fsnuffer above, I'm just not getting the right person at ATT.  It is infuriating!  

Please start a new thread on the topic vs using one from a number of yeara go.

What ports are you needing that you think are blocked?

AT&T does identify they will block ports (see https://about.att.com/sites/broadband/network) for  list. Only a limited number of these can be unblocked.

One last note. I have seen where the AT&T modem/router will act both as a bridge -and- will simultaneously run a limited NAT. It may have a default LAN ip like 192.168.0.1 and it may continue to listen at that ip even if it is configured as a bridge. It seems to run in a kind of hybrid mode. 

I had one client connect their equipment direct to the AT&T modem/router and called AT&T to set up a port forward. Then, when it didn't work, they converted to static IP bridging. The client setup their own router using a public ip for its WAN and the AT&T modem/router wsas set to bridge over the public ip. The client moved their equipment inside their own router at that point. However, the client NEVER removed the original port foward(s) from the AT&T modem/router. 

It was like the AT&T modem/router would take its own local port forward as a higher priority than handing off to its bridged ip. 

Strange configuration but I was called out to troubleshoot when they still could not get the port forwarding to work. Once I removed the port forward from the AT&T equipment, it began to function. 

Moral of the story--if you have an AT&T device bridging over a public ip, it is still possible there could be port forward entered in even if it is configured as a bridge. If you have an unexplained inability to port forward, you might want to check this.

Regards,

--Rick