Stuck at awaiting challange.
For no particular reason, when i connect to any server, my q3 gets stucked at the "awaiting challenge" step of connection process. I have reinstalled completely other version of q3, didnt help. Any suggestions? thx.. I'm without q3 almost a week and the abstinence syndrom is getting worse and worse:)
turned off firewalls?
Dunno, can't help you explicit. But i had this problem, when i made a firmwareupdate for my rooter, which did reset settings.
Problem was net_noudp was set to 1, means, the udp-protocol was deaktivated. When i changed it back to 0, it worked again.
Anyway, u can check on a simple way, if it is because of your rooter, just try the internet without ur rooter, means, plug the lan-cable direct into the dsl-box.
IF it is not ur rooter, u can try to backup ur q3configs/autoexecconfigs and then delete them from ur q3-folders. So u find out, if it is an config issue.
How do u know its a DSL connection? I just love ppl begging for help who never specify details of their hardware/software setup.
- what type of connection and hardware setup are we talking about?
- what firewall are we talking about,if any? (windows,hardware or 3d party software?)
- which version of windows,etc.
- what was the cause of this? u must know or at least try to remmember what did u last do to cause this problem?
Check this out as well:
For no particular reason, when i connect to any server, my q3 gets stucked at the "awaiting challenge" step of connection process. I have reinstalled completely other version of q3, didnt help. Any suggestions? thx.. I'm without q3 almost a week and the abstinence syndrom is getting worse and worse:)
try to generate another cdkey
v přídadě pokračujících problémů mi napiš na msn nebo icq
The white screen on startup with slight delay before quake starts is something i would call normal...but if u get a dead "hanging white screen" with no activity then some application is interfering with quake and isnt allowing it to start and this application is most probably the firewall cause u need to set the rule for q3.
But since this isnt your problem... we can blindly guess for ages whats going on. If ur 100% sure u havent touched anything,install/uninstall software or mess with firewall/AV then there is only one answer -> your ISP,or something network/server related that is probably out of your jurisdiction/range :>>
I had a similar problem,where u would get stuck with a msg "Please update your e+ client to the latest version..." altho it is ofc, allready up to date. When u get this msg,u can also wait forever or do multiple reconnects (sometimes up to 20-30 times,had to make a bind for /reconnect) and sometimes i get in server after 3,sometimes after 50 reconnects. This didnt happen on all servers, only on my favorite servers where i played the most
white screen at start is pb related, pb needs a timeout of 5 minutes, u can fix this to 5 seconds by renaming pb folder (note, disables client pb) if u got problems with the pb master server.
got same prob, dunno how to fix
if nobody knows of a solution...think ill quit q3 lol ive managed ok without it for a month and life is going pretty well...so wouldnt be that big of a deal
At least I posted in the right topic, right? Ok, firewall is Comodo, antivirus resident guard is Avira, system win xp 32. The problem is, I did NOTHING particular.. just turned the computer on for 30 minutes when I came back home from work, played, then turned it off and left the house. Day after in the morning, the problem was there and q3 was the first application i ran. The strange thing about that is, that sometimes after about 4 secs of awaiting challenge I connect normally, sometimes I await for the challenge forever and never connect. Also, the console says: resolving update to 192.246.40.56:27952 and then resolving authorize q3 to 192.246.40.56:27952... which is not even the ip of server I'm connecting to.. Last thing I have noticed, on startup of q3 the screen is white for few secs, didnt happen before, usually happened sometimes, when I tried to connect to some server and wasn't for some reason connected to the net (which I of course am..). thanks again for any suggestions..