Port Forwarding issue on BGW210

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.

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?

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.

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?

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.

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. 

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?

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?

Yes.

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?