Report, edit, etc...Posted by Staredit.Net Essence on 2005-11-29 at 18:42:49
there are only 3 triggers running, and they only run for a second in a 2v2...
Report, edit, etc...Posted by PCFredZ on 2005-11-29 at 19:25:11
Well, in THAT case it would be connection. 
Report, edit, etc...Posted by Staredit.Net Essence on 2005-11-30 at 02:33:42
broad band sucks, that or its my firewall!
Report, edit, etc...Posted by Mini Moose 2707 on 2005-11-30 at 15:20:54
start -> run -> cmd -> tracert useast.battle.net
This will pinpoint exactly where the lag is - your computer, your ISP, the other server, etc. The numbers should be low. *s are bad, that means it timed out.
This will pinpoint exactly where the lag is - your computer, your ISP, the other server, etc. The numbers should be low. *s are bad, that means it timed out.
Report, edit, etc...Posted by Merrell on 2005-11-30 at 16:27:52
You can also save it to a notepad (if you would like to paste it somewhere) by typing tracert useast.battle.net > C:\Tracert.txt
EDIT: I can't join any games on battle.net by the way. I fixed this last time by installing Service pack 2 and I DON'T want to do that again.
Here:
Tracing route to useast.battle.net [63.240.202.122]
over a maximum of 30 hops:
1 118 ms 107 ms 107 ms t3duat5.pennswoods.net [198.77.40.40]
2 104 ms 107 ms 107 ms rdr-at0.pennswoods.moose [198.77.40.29]
3 115 ms 107 ms 107 ms gwat0.pennswoods.net [198.77.40.1]
4 115 ms 117 ms 117 ms 12.124.192.37
5 126 ms 118 ms 117 ms gbr1-p50.phlpa.ip.att.net [12.123.137.6]
6 125 ms 117 ms 117 ms tbr2-p012501.phlpa.ip.att.net [12.122.12.105]
7 221 ms 128 ms 117 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
8 115 ms 118 ms 117 ms gar4-p300.wswdc.ip.att.net [12.123.9.73]
9 115 ms 128 ms 117 ms 12.122.255.2
10 115 ms 117 ms 117 ms mdf1-bi8k-1-eth-1-1.wdc1.attens.net [63.240.192.246]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
EDIT: I can't join any games on battle.net by the way. I fixed this last time by installing Service pack 2 and I DON'T want to do that again.
Here:
Tracing route to useast.battle.net [63.240.202.122]
over a maximum of 30 hops:
1 118 ms 107 ms 107 ms t3duat5.pennswoods.net [198.77.40.40]
2 104 ms 107 ms 107 ms rdr-at0.pennswoods.moose [198.77.40.29]
3 115 ms 107 ms 107 ms gwat0.pennswoods.net [198.77.40.1]
4 115 ms 117 ms 117 ms 12.124.192.37
5 126 ms 118 ms 117 ms gbr1-p50.phlpa.ip.att.net [12.123.137.6]
6 125 ms 117 ms 117 ms tbr2-p012501.phlpa.ip.att.net [12.122.12.105]
7 221 ms 128 ms 117 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
8 115 ms 118 ms 117 ms gar4-p300.wswdc.ip.att.net [12.123.9.73]
9 115 ms 128 ms 117 ms 12.122.255.2
10 115 ms 117 ms 117 ms mdf1-bi8k-1-eth-1-1.wdc1.attens.net [63.240.192.246]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Report, edit, etc...Posted by Deathawk on 2005-11-30 at 16:47:24
Have you tried the open support forums on Battle.net? I used to hang out there, I'm pretty sure they can help you.
Report, edit, etc...Posted by Merrell on 2005-11-30 at 16:55:21
Trust me, I asked there before, and I read through each post. This happens each time I reboot my computer. They, like usually, spammed these crappy battle.net support firewall pages. I went through each one, and none of them helped. In fact, I don't even have a firewall, but I KNOW that's the problem. Must be some hidden crap.
BTW: sorry for hijacking this thread <_<
BTW: sorry for hijacking this thread <_<
Report, edit, etc...Posted by Deathawk on 2005-11-30 at 17:54:53
I see.. you even posted the contents of the log to them?
Report, edit, etc...Posted by Mini Moose 2707 on 2005-11-30 at 19:01:32
It doesn't appear that you're even making it to the battle.net servers. I'd check with AT&T (who I dislike, by the way. 
).
).Report, edit, etc...Posted by Staredit.Net Essence on 2005-11-30 at 21:20:46
Umm. can someone tell me that in english? i just woke up and have had only a few hours of sleep and i feel farked up!
Report, edit, etc...Posted by Deathawk on 2005-11-30 at 21:23:17
The battle.net connection thing? I don't think it concerns you, so don't worry about it. Merrel sort of stole this whole thread with his problem... -_-
Report, edit, etc...Posted by Staredit.Net Essence on 2005-11-30 at 21:27:47
I would still like an ENGLISH way of fixing the problem, moment i changed from dial up i laged, so its got something 2 do with that!