Username:    Password:        Click Here To Signup     Forgotten Password
Main Menu
Online
Members: 0

Guests: 26

123.126.x.x forum
157.55.x.x comment
164.132.x.x dilbertplus
164.132.x.x forum
164.132.x.x forum
164.132.x.x forum
217.182.x.x forum
217.182.x.x forum
46.229.x.x forum
46.229.x.x forum
46.229.x.x user
46.229.x.x forum
46.229.x.x forum
46.229.x.x forum
46.229.x.x forum
46.229.x.x forum
46.229.x.x forum
51.255.x.x forum
51.255.x.x forum
51.255.x.x lgsl
51.255.x.x forum
51.255.x.x forum
54.166.x.x forum
66.249.x.x forum
68.180.x.x dilbertplus
78.46.x.x dilbertplus

Last Seen

Wussie Thu 17:43
Dodgeitorelse Thu 15:02
BRUT.me Wed 11:21
omidnw Wed 01:07
D1rty Tue 16:58

Newest Members

Forums
Wussie
Mon Nov 19 2012, 03:41PM

Posts: 413
Joined: Sun Mar 22 2009, 06:53AM
Registered Member #4938
Sadly, gametracker does not publish query ports for servers monitored, they would have made our life a lot easier if they did.

It turns out your whole problem was indeed the query port. I did some digging and found out that aarmy versions up to 2.5.0 use c_port=1716 and q_port=c_port+1 by default, while aarmy 2.8.5 uses q_port=7778, and this is what the vast majority seems to use nowadays.

As for 141.101.245.168:2302, that's not an aarmy server at all, it's Arma2 DayZ! it must be there by mistake...

Not working for you?
Don't forget to share the IP/ports of the offending server so that people can do tests and help you.
Oh, and if you're using a modified lgsl_protocol.php, make sure you disable the feed or it may NOT work!
Website
 

Jump:     Back to top


You are not logged in - Click Here To Signup

Username:    Password:   

Mini Buttons

.... © GreyCube.com - Richard Perry - Powered by e107.org