Temporary problem "awaiting challange"
Hello people,
yesterday while our war against wk i had a problem after the first map. I made a screenshot from the scoreboard and after that i did load our map cpm9. My Q3 hung up in the loadscreen. I typed /reconnect and i came to the "awaiting challange 1, 2, 3, 4" screen.
That was not normal, because the first what u c is usually "awaiting challange ..." and not "awaiting challange 1". I reconnected several times, and was not able to join on server, also when i restarted q3, also when i tryed to connect from kquery or ase. I also tried following.
- changing CD-Key
- restarting i-net to get a new ip
- restarting pc
- running q3 with the default q3config.cfg
- running a other q3
- turned off av-software and firewalls
.. and i came always to the screen "awaiting challange 1, 2, 3, ....45"
the strange thing on it, i was able to join each other server, just not that special one.
After the war i restarted the complete gameserver and was still not able to join the server. 1 hour later i tried again, and i was able again to join the server as normal as before.
Anybody had also this problem? I had it now meanwhile a couple of times, but first time on a war, and it is annoying to c, your team could have won if you would been there.
i think its server side problem. i think i had this problem in past too...
try to instal absolutly new q3a + pr1.32c+e+ mod and try to connect via this absolutly default version
so it cant be client side mystake : :roll:
@beazt -
Please, if you dont have anything more constructive to say, dont say anything at all.
Mow. Yes, i had this problem a few times too, most notably, on KO server during the mini freeze cup organized by HQ, and on separate few occasions. What seemed to help is lowering my /rate to some insanely low values, like 2000-3000.
Dunno if it would help in your case, it seems pretty damn weird.
Btw, i have a strong suspicion it's a bug in E+'s net code, which is pretty much a mess. Have no evidence on it tho, just a hunch. Maybe something with packet buffering? :scratch:
@mad : l o l on the pic
@topic : well yea happened to me also and if im not wrong more in the cases where the server had password(yes put it the good pass in ... ) . but worked fine with closing quake and reopen it after or that server is kind of busy cause u mentioned that it was on the cw vs wk meaning many connected almost in the same time or uptime of the server .. even if u said it happened only to u . its just some assumptions what ive wrote above
Btw, i have a strong suspicion it's a bug in E+'s net code, which is pretty much a mess. Have no evidence on it tho, just a hunch. Maybe something with packet buffering? :scratch:
could be netcode, since its bugged anyway (some people complaining about weird net since 1.03)
anyways sometimes, i just get a timeout (if i play longer on a server), i can join any other server without any problem, i can even a server with same ip, just different port (same root).
weird ;d
Mhh my first solution would be that the server is protected by ip tables or smth in any way so that there is a Max. limit of connections to the server ... or smth similar so that it just hasnt accepted any connections anymore (sure it sounds weird and simple somehow) ... but iam very sure it isnt a Client-Side problem and if you say that only you got problem, maybe you where exactly this "connection" which went over the limit ... can that be ?
If it would have been a serverside problem, the others would have had the same problem, further the problem wouldnt have been just temporary. further the server is on the same rootserver as a other running server with the same configs, except the gametype, and i was able to join my other server.