Cyber Monday: Get a FREE Samsung Galaxy S22 with eligible trade-in & Free Galaxy Buds2 - while supplies last!
Get superfast AT&T Fiber internet
phale98's profile

New Member

 • 

12 Messages

Fri, Aug 19, 2022 4:44 AM

Port Forwarding issue on BGW210

I am trying to open ports on the BGW210 on my residential fiber internet and cannot get the ports to open. For context in case it is needed, I am in a house and only use the ATT provided router. I followed the instructions on https://www.att.com/support/article/u-verse-high-speed-internet/KM1215101

The device is the name of the PC which will be running the server. After checking on canyouseeme while the server is running on the machine, I cannot see it. In addition any attempts to connect to the server fail.
Thinking it may be a fire wall issue on my end, I added blanket rules for the server machines firewalls that allow any traffic on that port inbound and outbound like this,
I have tried factory resetting the router both through the GUI accessed via internet browser and by holding the red reset button on the router for 20 seconds, and I still cannot seem to get this port to open. Any advice?
JefferMC

ACE - Expert

 • 

30.2K Messages

3 months ago

Everything looks correct.  The only thing that you might want to try is to Factory Reset the gateway and then retry setting up the Port Forwarding.

New Member

 • 

12 Messages

3 months ago

Hello, I have tried factory resetting both through the diagnostics -> resets tab when logging into the router, and by holding down the little red button until the lights on the router blink red, I still can't seem to get the ports to open. Is it possible for this router to be defective? Or for this to be blocked somehow on ATTs end?

JefferMC

ACE - Expert

 • 

30.2K Messages

3 months ago

AT&T has a document where they list the ports that they block in the network.  That can be found here:

https://about.att.com/sites/broadband/network

It is possible that the Gateway has a problem in the firmware version you have, or it could be an issue with the software on your PC.  Have you confirmed from some other device in your network that it can access port 25565 from within your local network (e.g. in a CMD window from another PC, telnet 192.168.1.whatever 25565 and see if the screen clears or you get the error message "Could not open connection to the host, on port 25565: Connect failed"

You may have to install the TELNET client because Windows no longer includes it by default.

(edited)

New Member

 • 

12 Messages

3 months ago

Okay so I'm not sure if I did this right, but first on the host machine I ran ipconfig to make sure I had the current correct local IPv4 like this

Then I used a second computer in the house that is wired to my network to do a telnet to that address and port 25565 while the server is running and got this
Do these commands look correct and if so, do you have any debugging steps to take from here?
JefferMC

ACE - Expert

 • 

30.2K Messages

3 months ago

Yes, looks like you did that correctly.  What this is telling you that your "server" computer at 192.168.1.247 is not accepting connections on port 25565.  This means that we cannot tell if your port forwarding is working or not, because the destination of that port forward isn't accepting the connections.

So, we need to focus on why your computer isn't accepting those connections.  

Try doing a

netstat -a | findstr ":25565"

on your "server" computer.  The purpose of that is to see if any software has the port open.  If not, then something is wrong with the server software.  If so, then maybe the firewall isn't working like it appears it should.  

On the other hand, all these diagnostics have been assuming that you've had the server software up and running and accepting connections while doing these tests.  If you were trying to test it before you started the software that is supposed to be using the port, then none of these diagnostic tests (including CanYouSeeMe) will be useful; start the software and start over.

(edited)

New Member

 • 

12 Messages

3 months ago

Ok I have ran the netstat command, I think that the results are saying that it is listening on that port while the server adding a screen grab for reference. The first attempt seemed to hang a bit, so I stopped it with cntrl c and started over. 

JefferMC

ACE - Expert

 • 

30.2K Messages

3 months ago

Yep, that does show something listening.  So... have you tried looking at the Windows Firewall monitor to see if you can tell if its passing or dropping the requests?

New Member

 • 

12 Messages

3 months ago

To clarify on this are you suggesting I try to telnet from another computer again and see if the connection is dropped in the Windows firewall logs?

JefferMC

ACE - Expert

 • 

30.2K Messages

3 months ago

Yes.

New Member

 • 

12 Messages

3 months ago

Sorry for the delay, I have the host PC set up running the server and ran the telnet command. I did not see any dropped packets in the pfirewall.log. All packets seemed to be marked receive or send, but doing a cntrl f for drop or success in the file yielded zero results. I have set up the logging as screenshots indicated.

Does this indicate that the packets are not being dropped?
Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.