Jump to solution

Unable to connect to blizzard service

sbeare87
Grasshopper

There's an issue preventing me from connecting to the americas realm on Blizzard's Starcraft 2 game. Here's what I get when I ran WinMTR:

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                          GT-AC5300-5D40 -    0 |   65 |   65 |    0 |    0 |    6 |    0 |

|                               70.77.0.1 -    0 |   65 |   65 |    7 |   11 |   20 |    8 |

|          rc3no-be116-1.cg.shawcable.net -    0 |   65 |   65 |    8 |   13 |   22 |   13 |

|                           24.244.57.181 -    0 |   65 |   65 |    8 |   19 |  168 |   10 |

|                             24.244.57.5 -    0 |   65 |   65 |    8 |   14 |   23 |   12 |

|            rc3no-be214.cg.shawcable.net -    0 |   65 |   65 |    6 |   15 |   24 |   15 |

|            rc2wt-be100.wa.shawcable.net -    0 |   65 |   65 |   23 |   27 |   37 |   26 |

|     rc6wt-tge0-10-0-11.wa.shawcable.net -    0 |   65 |   65 |   28 |   37 |   85 |   36 |

|              ae1-br02-eqse2.as57976.net -    0 |   65 |   65 |   55 |   63 |  137 |  137 |

|                   No response from host -  100 |   13 |    0 |    0 |    0 |    0 |    0 |

|         et-0-0-1-pe01-eqch2.as57976.net -    0 |   65 |   65 |   56 |   60 |   72 |   68 |

|                           24.105.62.129 -    0 |   65 |   65 |   55 |   59 |   71 |   69 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

Also note that I should probably be routed through their uswest IP, which when I tested with WinMTR does connect properly (I live in Calgary). Unless of course their login service requires authentication to both uswest and useast...

Edit: Sorry if someone else has posted this issue recently... I did see an older post but figured I should start a new one.

Labels (1)
1 Solution

Accepted Solutions
Jump to solution

-- I do not see any problem with your trace.  The output:...

mdk
Grand Master

@sbeare87 -- I do not see any problem with your trace. 

The output: No response from host -  100 |   13 |    0 |    0 |    0 |    0 |    0 |

just indicates that this one router is either too busy to respond to such low-priority "overhead" traffic, such as a "trace" request, or it is deliberately  configured to _not_ respond to that type of packet.

I see that your trace goes through "CG" (Calgary) to "WA" (Shaw's packet-interchange point in Washington State) and then to Seattle.

I am west of you, namely in BC, and my "tracert" output is similar:

5 108 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
6   16 ms rc6wt-tge0-10-0-10.wa.shawcable.net [66.163.68.66]
7   67 ms ae1-br02-eqse2.as57976.net [137.221.73.35]
8    * * * Request timed out.
9    62 ms et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51]
10  61 ms 24.105.62.129

Trace complete.

namely crossing over the CAN/USA border -- from Shaw's network to a router in Washington State.

Maybe, "eqse2" references "SEattle", and "eqch2" references "CHicago" ???

Note that the IP-address "24.105.62.129"  is within the range: 24.105.0.0 - 24.105.63.255 that is allocated to: BLIZZARD ENTERTAINMENT INC

So your packets _are_ reaching Blizzard.

 

 

 

 

 

 

View solution in original post

Reply
Loading...
2 Replies
Jump to solution

-- I do not see any problem with your trace.  The output:...

mdk
Grand Master

@sbeare87 -- I do not see any problem with your trace. 

The output: No response from host -  100 |   13 |    0 |    0 |    0 |    0 |    0 |

just indicates that this one router is either too busy to respond to such low-priority "overhead" traffic, such as a "trace" request, or it is deliberately  configured to _not_ respond to that type of packet.

I see that your trace goes through "CG" (Calgary) to "WA" (Shaw's packet-interchange point in Washington State) and then to Seattle.

I am west of you, namely in BC, and my "tracert" output is similar:

5 108 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
6   16 ms rc6wt-tge0-10-0-10.wa.shawcable.net [66.163.68.66]
7   67 ms ae1-br02-eqse2.as57976.net [137.221.73.35]
8    * * * Request timed out.
9    62 ms et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51]
10  61 ms 24.105.62.129

Trace complete.

namely crossing over the CAN/USA border -- from Shaw's network to a router in Washington State.

Maybe, "eqse2" references "SEattle", and "eqch2" references "CHicago" ???

Note that the IP-address "24.105.62.129"  is within the range: 24.105.0.0 - 24.105.63.255 that is allocated to: BLIZZARD ENTERTAINMENT INC

So your packets _are_ reaching Blizzard.

 

 

 

 

 

 

Reply
Loading...
Jump to solution

Oh ok, thanks for that information... so then I would exp...

sbeare87
Grasshopper

Oh ok, thanks for that information... so then I would expect that it simply wouldn't reach the destination (and thus I wouldn't see that last line present in the trace) if it was an issue with the route taken.

0 Kudos
Reply
Loading...
TALK TO US
Need more help?