Server is for low pings only

(FstFngrz) #1

Server is for low pings only - ET join server error

Not really a big deal, but would be nice to be addressed at some point.
Doesnt matter if I ping 20 or 300, it still pops up almost everytime I try to join a server. I thought it may just be my setup , but listening to others its not. It still does it on the new beta patch’s also. It has really never effected me, as I always just reconnect and all is OK. But I have had over 10+ different people tell me that they could not join a few popular server’s cause “its for low pings only”.

again not really a big deal, but it does seems to keep people out of servers.
( It happened yesterday when a PunkBuster expert was off to ECGN’s 64 Player server to investigate the excitement of the day. I thought it was really cool that PunkBuster had responded Within the hour)

(Vengeance) #2

I get this quite a lot when joining a server for the first time and as soon as i click recconect it lets me through.

Its annoying since i have a steady ping of around 50 on UK servers and the time it takes to get through could mean i lost my slot and have to wait for someone to leave :frowning:

(Cyber-Knight) #3

what’s the point of having that message when you press on reconnect, it goes away.

it’s always gone away when I hit reconnect

(Ragnar_40k) #4

I have this message sometimes too and have to press the “Reconnect” button. My first thought was that this is related somehow to my provider, but I never had this problem with RtCW.

(Spookstah) #5

In the server config file an admin can set a maxping, we have set it to 325 atm.

When a new player joins the server most of the time your ping is displayed as 999, i think this causes the problem.

(SCDS_reyalP) #6

Every q3 based game I’ve ever played has done this at one time or another…

/reconnect

If it happens a lot, maybe there is something weird about your connection ? tracerouting the server might show it up, though it is unlikely there will be anything you can do.

(fat boost) #7

the weird thing about that error is it seems to have literally nothing to do with your ping at the time.

I think it’s an old error from like Q3A or something and nobody ever figured out how the hell to fix it.

(Lekdevil.NL) #8

My take on it is this (best guess but unverified): when you connect to a server for the first time, your system is still busy loading stuff into memory. This messes up (i.e. delays) the response to the server’s challenge, making the server think that your ping is higher than it actually is. When you do a \reconnect, everything is already loaded so the response gets sent out quicker.

How much memory do you have, what is your com_hunkmegs set at and what are your other system specs?

(gurb) #9

When a client connects to the server I think it sends off an initial packet or probe. This is what you can see in the server console:

Client 62 connecting with 264 challenge ping

my guess is that if the challenge ping from the client is lower than the sv_maxping value the server responds with the “Go away you lousy HPB”.

There can be reasons why the initial packet / probe use longer time to get to the server (or, is it from the server to the client and back again?). The most obvious ones are your connection, your ISP’s connection to the server, But then again both the client and the server could be poorly configured or running out of resources.

(Lt. Jones) #10

I get this every single time I join a server now. I’m on a cable modem, and i’m not using ASE, GSA, or anything else. Very annoying :banghead:

(MAN-AT-ARMS) #11

Yeah…I (and I’m sure others) have submitted this bug to id software. On initial connect ping is reported much higher than it actually is. Not sure if this is a client side or server side bug…but it’s been there since the beginning.

(twiFight) #12

Yep, I also have this problem. Using All Seeing Eye or not makes no difference. And no, my ping is not high (around 40-50 stable). Happens with almost all servers. Since a lot of people are having this problem it doesn’t strike me as an ISP problem (since people use different ISPs).

I would really like this bug solved, since it happens so often and has no use at all; reconnecting ALWAYS solves it.

([B]Visa) #13

yeah happens quite often here too…

So far in my researching about the problem I basically found out I just have to grin and bear it :confused:

Sucks to lose a slot to that kind of “error”, hopefully this could get addressed in a patch in the future.

Ike-T