When i’m trying to connect to ET servers, it’ll take a really long time to actually connect (while it sits there saying awaiting connection…#)
Also, my Q3 does a similar thing but instead of “Awaiting Connection…#”, it goes straight to “Awaiting Challenge…#” and takes forever.
can anyone help me out?
First, some questions:
How long is ‘really long’ ? 10 seconds ? 1 minute ?
What kind of connection are you on ? (DSL, cable, dail up, carrier pigeon) ?
Do you lag in game after you connect ? If you haven’t already, turn on the lagometer with cg_lagometer 1. This thread: http://bani.anime.net/banimod/forums/viewtopic.php?t=3550 explains what it shows.
The most likely cause is some network problem between you and the server. Assuming it happens on all servers, then it is near your end. This could be caused by some problem with the actual hardware, or by congestion, or by viruses/trojans/P2P software on your computer.
If you have checked for viruses and trojans, and made sure that all P2P software is off, and you still have lag, then you need to troubleshoot your connection. You can use tracert and ping to do this. Just ask if you need help with that.
I am not MillT, but I know that he sometimes has to wait up to 10 minutes to get connected to servers. In game, once he has connected, he does not lag, and his lagometer is quite stable. As he usually plays on servers in his local area, he typically pings in the 15-30 range during matches.
yeah the time varies…never more than 10 minutes or so, but never instantaneous as before
i’m on comcast cable =/
no lagging in game largely
perhaps its something on my router, but its a new wireless d-link, and i only know the ins-and-outs of linksys
wireless stuff can be picky. I would test for packetloss on your wireless link. Use tracert to find the next hop after your wireless, and then use ping -n 100 -l 1000 and see if there is loss or large ping times. (-n 100 means 100 packets, which gives you a reasonable sample size. -l 1000 means the packets should be 1000 bytes long, which tends to show up network problems more effectively than the small size). If the wireless link turns out not to be the problem, you can use the same procedure subsequent hops to find out exactly where it is.
If you can arrange to temporarily use wired ethernet instead, that would also be a way of finding out if it is the wireless is to blame.
Even if you don’t feel laggy while playing, you may be getting some packet loss. If you haven’t allready, turn on the lagometer and watch for red.
oh yeah, i forgot to mention
it does it regardless of how i connect to the router (whether it be wireless or wired)
yeah no sign of weirdness during play on the lag-o-meter