Ports 27015-27017 reported as closed even though I set them as open

[Vengeance1020]

I am hosting a game server that requires that ports 27015-27017 be open. I have done that and it was working up until this point. I found that as of last night, when I attempted to start the game server again, that none of my friends could join. I checked my ports using two port check tools, one reported those ports as timing out, the other reported them as closed. I can still access port 3389 for remote desktop just fine. I have gone through the firewall settings and nothing suggests those ports being closed. They are added as an exception in the router to pass through the firewall. I have rebooted my server machine but have not been able to reboot the router if that were a necessary step to troubleshoot this problem. Of course I shouldnt need to reboot the router for the port forwarding to take effect, I didnt have to the first time and when I forwarded 3389. I have them set to the right protocol as my friends were able to connect and the protocol was the same then as it is now, I have checked. I cannot figure this out, any ideas?

[Donut417]

1 hour ago, Vengeance1020 said:

I am hosting a game server that requires that ports 27015-27017 be open. I have done that and it was working up until this point. I found that as of last night, when I attempted to start the game server again, that none of my friends could join. I checked my ports using two port check tools, one reported those ports as timing out, the other reported them as closed. I can still access port 3389 for remote desktop just fine. I have gone through the firewall settings and nothing suggests those ports being closed. They are added as an exception in the router to pass through the firewall. I have rebooted my server machine but have not been able to reboot the router if that were a necessary step to troubleshoot this problem. Of course I shouldnt need to reboot the router for the port forwarding to take effect, I didnt have to the first time and when I forwarded 3389. I have them set to the right protocol as my friends were able to connect and the protocol was the same then as it is now, I have checked. I cannot figure this out, any ideas?

Your ISP found out your running a server and has blocked the ports? 

[Vengeance1020]

Just now, Donut417 said:

Your ISP found out your running a server and has blocked the ports? 

Shouldn't have, I even opened ports 27000 to 27050 and they were all closed immediatly

[Lurick]

Did you set a static IP address on the server?

[Vengeance1020]

Just now, Lurick said:

Did you set a static IP address on the server?

I have locked the IP for the network I use to host my game, I set it on windows and whenever I connect it stays the same. so IP address is not a concern.

[Lurick]

6 minutes ago, Vengeance1020 said:

I have locked the IP for the network I use to host my game, I set it on windows and whenever I connect it stays the same. so IP address is not a concern.

Well ports are either closed because your ISP is blocking them, they aren't forwarded correctly, or nothing is listening at the address they are forwarded to.

If you have a static IP address on the server and you're forwarding to that address they should be open (obviously they aren't for some reason), unless something else grabbed that port range or the application isn't listening on those ports for whatever reason.

 

Try to run the command 'netstat -nab' from an elevated command prompt and see if the application is really listening on those ports, it might not be for some reason.

[Vengeance1020]

7 minutes ago, Lurick said:

Well ports are either closed because your ISP is blocking them, they aren't forwarded correctly, or nothing is listening at the address they are forwarded to.

If you have a static IP address on the server and you're forwarding to that address they should be open (obviously they aren't for some reason), unless something else grabbed that port range or the application isn't listening on those ports for whatever reason.

 

Try to run the command 'netstat -nab' from an elevated command prompt and see if the application is really listening on those ports, it might not be for some reason.

Well since I have an AT&T box, all I had to do was select my computer (It probably forwards to the detected IP of the selected computer) and add the application and add port range and protocol and save it and I was done. Worked for port 3389 and for the game server ports up until now. My best guess for the application not listening is that it did just update, I am looking into that

[Vengeance1020]

18 minutes ago, Lurick said:

Well ports are either closed because your ISP is blocking them, they aren't forwarded correctly, or nothing is listening at the address they are forwarded to.

If you have a static IP address on the server and you're forwarding to that address they should be open (obviously they aren't for some reason), unless something else grabbed that port range or the application isn't listening on those ports for whatever reason.

 

Try to run the command 'netstat -nab' from an elevated command prompt and see if the application is really listening on those ports, it might not be for some reason.

I did the command and port 27017 shows up under the game name, none of the other ports, 27015 is the connecting port so it should show up

[Mornincupofhate]

You either didn't set them up properly, or your ISP blocked them to keep you from running game servers. Most likely they blocked you.

 

Whose your provider?

[Vengeance1020]

Just now, Mornincupofhate said:

You either didn't set them up properly, or your ISP blocked them to keep you from running game servers. Most likely they blocked you.

 

Whose your provider?

AT&T, strange thing I discovered. Those ports still report as closed and yet I ran the server for a while (forgot I had it running for a test, was shutdown when checking ports and was online when checking ports a second time, closed both times) and I saw people connecting to the server, even though the ports were reported as closed. I suppose the firewall in the router is having a panic attack or something