|
|
 |
|
|
Pages: 1
Connect to certain games
(Click here to view the original thread with full colors/images)
Posted by: G_Force
I didn't want to retype this, so here is the converation I had with RoadRunner tech support:
Chase: I have been playing starcraft for some time, and until recently never
had a problem. Two friends of mine are also on a roadrunner line across town,
and for some reason I have been unable to join their Starcraft games. I am not
behind a firewall or router, he has two computers behind a switch.
Janice: Thank you. Let's see what we can do to resolve this issue.
Janice: Are you experiencing any problems with normal browsing?
Chase: No, everything is fine, in fact, I can jion all other starcraft games
except for theirs
Chase: And they, likewise, cannot join mine
Janice: Ok, please be aware that Road Runner does not provide any technical
support for online gaming issues. Please contact the administrators of the
Starcraft game servers for further assistance with this issue.
Chase: Thanks, it's just I'm exhausing all possible issues.
Chase: disconnected
Janice: disconnected
So, does anyone know why this might be?
-Chase Mitchell
Posted by: NegotiatorSmith
If other people are able to join your friends' games, the problem is simply that the connection latency between you and your friend is too high. If no one can join your friends' games, they need to open port 6112 UDP inbound in any firewalls they're behind.
Posted by: G_Force
That's just the thing. The latency ISN'T too high.
We can send files between each other at high speeds, and ping each other in a few milliseconds.
I can't join their games, they can't join mine. We can all join other peoples games, and other people can join ours.
-G
Posted by: NegotiatorSmith
If the latency of a connection between you guys isn't a problem, there are only two other possibilities that I can think of:
a. For some odd reason Roadrunner is preventing you guys from sending data to each other on port 6112 UDP. This is obviously something you'd have to ask Roadrunner about.
b. For a while now, I have been questioning my current understanding of how Starcraft games work. I know that when the game starts each player sends data on port 6112 UDP to each other player and Battle.net's servers aren't involved, however I'm not completely sure about what happens before the game starts. If the latency error message indicates a comparison between the host's and the joiner's latencies to the Battle.net server they're connected to and not to each other, that could indicate that there is a big difference between the latencies and would explain why they can't join the same game.
I'd suggest that each of you run a trace route to the Battle.net gateway you're connected to (i.e. useast.battle.net) and see what ping times you're getting. If you ping the gateway you won't get a response, so you need to run a trace route to see the amount of time it takes the ICMP packet to get from one hop to the next. If you have an average ping time of oh, 100 ms and your friend has something like 400, that could explain the problem.
Other than the two theories I presented, there's nothing else I can suggest. It's not a firewall issue on your ends because other people can join your games, and your pings to each other indicate a good latency.
Posted by: G_Force
In command prompt, friend and I both pinged uswest.battle.net -- All 4 timed out.
I did a traceroute:
http://www.socialwarp.net/trace.bmp
(Sorry it's in BMP, I just reinstalled window, no photoshop yet)
I tried pining his IP, timeouts, he tried pinging me, timeouts.
-G
Posted by: NegotiatorSmith
 Quote:
|
In command prompt, friend and I both pinged uswest.battle.net -- All 4 timed out.
|
That's why I said "if you ping the gateway you won't get a response". 
That's a nice graphical analysis you have there, but I want to see the numbers, not the physical locations that the packet is going to. Output your trace route results to a file by doing this:
tracert uswest.battle.net > tracert.txt
Pinging each other won't work if you guys have firewalls up that block ICMP packets.
Posted by: G_Force
Remember, I can connect to b.net just fine.
tracert.txt::::
Tracing route to uswest.battle.net [63.241.83.7]
over a maximum of 30 hops:
1 10 ms 9 ms 10 ms 10.42.192.1
2 10 ms 9 ms 10 ms RDC-24-164-224-145.new.rr.com [24.164.224.145]
3 12 ms 11 ms 12 ms srp0-0.gnbywi1-rtr1.new.rr.com [24.164.224.26]
4 27 ms 25 ms 25 ms so0-1-1.kscymoL3-rtr1.kc.rr.com [24.94.160.25]
5 26 ms 25 ms 29 ms so0-0-2.chcgilL3-rtr1.kc.rr.com [24.94.161.106]
6 38 ms 38 ms 37 ms pop1-chi-P7-0.atdn.net [66.185.136.109]
7 39 ms 39 ms 37 ms bb1-chi-P0-0.atdn.net [66.185.141.84]
8 38 ms 39 ms 37 ms pop2-chi-P0-0.atdn.net [66.185.148.65]
9 49 ms 38 ms 41 ms aol-gw.cgcil.ip.att.net [192.205.32.237]
10 41 ms 38 ms 42 ms tbr1-p010401.cgcil.ip.att.net [12.123.6.66]
11 76 ms 72 ms 72 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
12 72 ms 72 ms 70 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
13 71 ms 71 ms 72 ms idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.255.222]
14 78 ms 78 ms 78 ms mdf2-bi8k-2-eth-2-1.rwc1.attens.net [216.148.209.14]
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.
Posted by: NegotiatorSmith
I know that you can connect to Battle.net just fine; we're doing the trace route to see what ping times you're getting at each hop when a packet goes from you to the Battle.net gateway you're playing on. The point of doing this was to compare your results to your friend's results and see if there is a big difference in the ping times.
Posted by: Derigitable
Many people on bnet are experiencing this same problem with their cable connections, i.e., not being able to host games, lagging out of games.
Their pings are excellent.
It's nothing to do with your computers. We are experiencing the same problem with TimeWarner. I have done everything possible with these computers from opening udp ports to reformatting the computers, stripping them down from all possible programs that could possibly be interfering. Completely eliminating all firewall issues. Nothing has helped.
It's like packets are being sent that are causing this problem. It happens with such regularity, almost like clockwork. I think that TimeWarner is just too stingy to place more cables. You will find that if you're playing on line late at night that you won't have these same problems.
Our computers are networked, so it might be that bnet has issues with networked computers, but I have almost eliminated this as a source of the problem too because I erased all the networking files from some of the computers and hooked one computer straight into the cable modem and still experienced the problem. Also, I am temporarily away from my family, hooked up on cable with Tele-Media Cable, and their service has worked impeccably, and I have not erased those same networking files from this computer. (We have several computers.)
We have dial-up too, and dial-up has been more reliable than TimeWarner Cable.
Posted by: NegotiatorSmith
I use Comcast cable and I haven't had any problems with Starcraft.
Quote:
|
You will find that if you're playing on line late at night that you won't have these same problems.
|
This does not surprise me in the least, as cable connection bandwidth is shared among users in a certain area, like a neighborhood. During peak usage hours, people are often downloading big files, sucking up connection bandwidth and causing latency issues for others.
Quote:
|
Our computers are networked, so it might be that bnet has issues with networked computers, but I have almost eliminated this as a source of the problem too because I erased all the networking files from some of the computers and hooked one computer straight into the cable modem and still experienced the problem.
|
I have talked to many people about Starcraft connection problems on their cable connections, and most of those people were behind NAT routers or PCs running Internet connection-sharing software. The cable connection itself wasn't at fault, it was the router or "host" PC. Starcraft doesn't seem to be very NAT-friendly, however I have gotten it to work without any problems behind three different routers (a Linksys and two Netgears). About all you can do is try forwarding port 6112 UDP to your computer or get a better router.
|
|
|
|
|
