ejziponken wrote:

Well you dont even know if there is a scanning issue. All you are saying is that its most likely not. You are just guessing at this point.


My last post absolutely confirmed that there are no scanning issues at our end, as per the response I received from the Gametracker server administrator.

chimaera500 wrote:

My last post absolutely confirmed that there are no scanning issues at our end, as per the response I received from the Gametracker server administrator.


What's happening with my server? Are there any logs saying why the connection failed?

I'm on a different network (and in a different country) than where my server is hosted but I can connect via HLSW:


The entire 27000 - 27500 port block is open on my firewall so I don't see why GT can connect to 27015 but not 27005 or 27010

I can see that your servers are all visible on HLSW.
Is it possible there are some differences in configuration between the registered server (149.56.28.95:27015) and the two you are not able to register?

I just checked the .cfg files and they are all the same, the only differences are tick rates that are optimized to reduce CPU usage for the larger maps but that shouldn't affect scanning

@ejziponken - Feel free to update your topic if you have any additional question. I gave you a specific answer for a specific reason.

@gurgle528 - I just attempted to query your servers 149.56.28.95:27005 and 149.56.28.95:27010 and they are not responding. Please review your firewall to ensure TCP/UDP ports are open and reload your rules - or temporarily disable the firewall for a couple minutes to see if it works.

Alright, I disabled my firewall and tried adding 149.56.28.95:27010 and 27005 twice each but still no luck.

Here's the UFW rules I'm using by the way:

burn wrote:
@ejziponken - Feel free to update your topic if you have any additional question. I gave you a specific answer for a specific reason.

@gurgle528 - I just attempted to query your servers 149.56.28.95:27005 and 149.56.28.95:27010 and they are not responding. Please review your firewall to ensure TCP/UDP ports are open and reload your rules - or temporarily disable the firewall for a couple minutes to see if it works.

Youre saying problem is on my end, Im saying its on your end (not scanning maybe but in the DB). Cant really add anything more. So im good.

gurgle528 wrote:
Alright, I disabled my firewall and tried adding 149.56.28.95:27010 and 27005 twice each but still no luck.

Here's the UFW rules I'm using by the way:

I just tested again and I was FINALLY able to get your two servers to respond at all on HLSW. The problem is that query to your server timed out at least 75%+ of the time. I'd suggest that these timeouts may be causing your problems. The scanner allows a maximum response time.

@ejziponken - I'm sorry that our pointers didn't help you. We apologize if we cannot get too involved in your system and network configuration (time, expertise, and liability). Have a great day.

burn wrote:

I just tested again and I was FINALLY able to get your two servers to respond at all on HLSW. The problem is that query to your server timed out at least 75%+ of the time. I'd suggest that these timeouts may be causing your problems. The scanner allows a maximum response time.

Strange. Do you have any idea what could be causing these timeouts? Has this happened to anyone before?

I can recall "timeout issues" on other servers in the past, but it's been so rare (that I've seen at least) that it would be hard to pinpoint. Since you tried disabling your firewall (I assume it's the only blocking software you have), I would check your resources (network, cpu, memory, etc) to see if anything is peaking that could slow things down.